Triple
T36567930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Hall |
E902028
|
entity |
| Predicate | primarySpaceOf |
P55012
|
FINISHED |
| Object | Winter Gardens |
E1680896
|
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: Winter Gardens | Statement: [Main Hall, primarySpaceOf, Winter Gardens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySpaceOf Context triple: [Main Hall, primarySpaceOf, Winter Gardens]
-
A.
primaryFor
chosen
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
B.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
C.
primaryLocationIn
Indicates that an entity’s main or most significant location is within or at the referenced place.
-
D.
primaryUnit
Indicates that one entity serves as the main or principal unit associated with another entity, typically among multiple possible units.
-
E.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f90c74d8819084b7065e698c5d4b |
completed | June 23, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.