Triple
T1296788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tottenham Hotspur Stadium |
E27669
|
entity |
| Predicate | hasLongBar |
P28380
|
FINISHED |
| Object | Goal Line Bar |
—
|
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: Goal Line Bar | Statement: [Tottenham Hotspur Stadium, hasLongBar, Goal Line Bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongBar Context triple: [Tottenham Hotspur Stadium, hasLongBar, Goal Line Bar]
-
A.
hasUpperBarLength
Indicates that an entity possesses an upper bar whose length is specified or constrained by the related value or object.
-
B.
hasLowerBarLength
Indicates that one entity’s bar length is shorter than the bar length of another entity.
-
C.
hasPoolBar
Indicates that a place or facility includes a bar located in or directly adjacent to a swimming pool.
-
D.
isLongRunning
Indicates that an action, process, or operation continues for an extended duration, typically longer than is usual or expected.
-
E.
hasBarrelConfiguration
Indicates a relationship where an object is characterized by or assigned a specific arrangement or configuration of its barrel or barrels.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c3b9ebdc819098de4d3288201bc1 |
completed | March 1, 2026, 10:54 p.m. |
Created at: March 1, 2026, 7:51 p.m.