Triple
T23649133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Down’ards |
E584120
|
entity |
| Predicate | usesGoalLocation |
P43296
|
FINISHED |
| Object | Down’ards goal at Clifton |
—
|
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: Down’ards goal at Clifton | Statement: [Down’ards, usesGoalLocation, Down’ards goal at Clifton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGoalLocation Context triple: [Down’ards, usesGoalLocation, Down’ards goal at Clifton]
-
A.
targetLocation
chosen
Indicates the specific place or destination toward which an action, movement, or effect is directed.
-
B.
approachLocation
Indicates that an entity moves closer to or heads toward a specified location.
-
C.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
D.
machineGoal
Indicates that a machine or automated system has a specific objective, target state, or outcome it is intended or programmed to achieve.
-
E.
isIntermediateGoalOn
Indicates that one goal serves as a necessary or contributing intermediate step toward achieving another goal within a larger plan or process.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b287606881909926de5efd882a76 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.