Triple
T23648944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Shrovetide Football |
E584115
|
entity |
| Predicate | goalDistanceApart |
P150079
|
FINISHED |
| Object | approximately three miles |
—
|
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: approximately three miles | Statement: [Royal Shrovetide Football, goalDistanceApart, approximately three miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalDistanceApart Context triple: [Royal Shrovetide Football, goalDistanceApart, approximately three miles]
-
A.
distanceFromGoal
Indicates the measured or estimated separation between an entity’s current position and its intended goal or target state.
-
B.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
C.
distanceOfNotableGoalApprox
chosen
Indicates an approximate measurement of how far away a notable goal or target is.
-
D.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
E.
haveTypicalApproachDistance
Indicates that there is a characteristic or standard distance typically maintained when approaching something.
- 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.