Triple
T33258068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace Hall |
E851430
|
entity |
| Predicate | hasHistoricComponent |
P160886
|
FINISHED |
| Object | Leeman-Turner Arena |
E2052584
|
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: Leeman-Turner Arena | Statement: [Grace Hall, hasHistoricComponent, Leeman-Turner Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricComponent Context triple: [Grace Hall, hasHistoricComponent, Leeman-Turner Arena]
-
A.
hasHistoricMP
Indicates that an entity is or has been represented by a specific Member of Parliament at some point in the past.
-
B.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
-
C.
hasHistoricSegment
chosen
Indicates that an entity includes or is associated with a segment that has historical significance or originates from a past version or period.
-
D.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
E.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35a65890ac8190bd0ecabd3ba64c76 |
completed | June 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 1, 2026, 1:31 a.m.