Triple
T31115869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrison Square project |
E793083
|
entity |
| Predicate | primaryAnchor |
P55012
|
FINISHED |
| Object | Parkview Field |
E224953
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Parkview Field | Statement: [Harrison Square project, primaryAnchor, Parkview Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAnchor Context triple: [Harrison Square project, primaryAnchor, Parkview Field]
-
A.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
-
B.
primaryReferent
Indicates that one entity is the main or most salient referent associated with another entity among potentially multiple candidates.
-
C.
primaryMount
Indicates that one entity serves as the main or default mount (attachment or support point) for another entity.
-
D.
primaryFor
chosen
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
E.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a71f236dc8190a50faff2ab9c5f55 |
completed | June 11, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:04 p.m.