Triple
T9432365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moor Lane |
E227412
|
entity |
| Predicate | hasStandsOnAllSides |
P88875
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Moor Lane, hasStandsOnAllSides, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandsOnAllSides Context triple: [Moor Lane, hasStandsOnAllSides, yes]
-
A.
hasSideWalls
Indicates that an object or structure possesses side walls as part of its physical configuration.
-
B.
hasStandsType
Indicates that an entity has or is associated with a particular type or category of stands (e.g., display stands, support stands, or similar structures).
-
C.
isFreeStanding
Indicates that an object or structure stands independently without needing external support or attachment.
-
D.
hasAllSeaterStands
Indicates that all stands or spectator areas associated with an entity consist entirely of seated accommodations, with no standing-only sections.
-
E.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
- F. None of above. chosen
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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e6059bc8190a7e98aef3caabd0b |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:49 p.m.