Triple
T5631042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northumberland Development Project |
E147830
|
entity |
| Predicate | notableFeatureOfMainStadium |
P61000
|
FINISHED |
| Object | retractable pitch for NFL |
—
|
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: retractable pitch for NFL | Statement: [Northumberland Development Project, notableFeatureOfMainStadium, retractable pitch for NFL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFeatureOfMainStadium Context triple: [Northumberland Development Project, notableFeatureOfMainStadium, retractable pitch for NFL]
-
A.
notableStadium
Indicates that an entity is a stadium that is particularly prominent, famous, or significant in some notable way.
-
B.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
C.
stadiumFeature
Indicates that a stadium possesses or includes a particular feature, characteristic, or facility.
-
D.
notableFeatureOn
chosen
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
E.
mainStadiumNickname
Indicates the commonly used nickname by which a main stadium is known.
- F. None of above.
Provenance (3 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225cdcdc819095034f12c39ef755 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.