Triple
T19683138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shed End |
E472642
|
entity |
| Predicate | isEndStand |
P136906
|
FINISHED |
| Object | south end of Stamford Bridge (commonly regarded) |
—
|
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: south end of Stamford Bridge (commonly regarded) | Statement: [Shed End, isEndStand, south end of Stamford Bridge (commonly regarded)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndStand Context triple: [Shed End, isEndStand, south end of Stamford Bridge (commonly regarded)]
-
A.
isStandOf
Indicates that one entity serves as the Stand (a supernatural or personified power) belonging to or associated with another entity.
-
B.
isHomeEndFor
Indicates that something serves as the final destination, endpoint, or concluding location for a journey, process, or sequence.
-
C.
endOfSeriesStatus
Indicates that a series, sequence, or collection has reached its final state or completion status.
-
D.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
E.
isFinishLineOf
Indicates that something serves as the finish line or endpoint for a particular event, race, or process.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641c126b88190820281058a1e7793 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:45 p.m.