Triple
T1736492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chariots of Fire |
E37929
|
entity |
| Predicate | depictsSport |
P6214
|
FINISHED |
| Object | track and field |
—
|
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: track and field | Statement: [Chariots of Fire, depictsSport, track and field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsSport Context triple: [Chariots of Fire, depictsSport, track and field]
-
A.
representsInSport
Indicates that one entity serves as an official representative of another entity within the context of a particular sport or sporting domain.
-
B.
sportFocus
chosen
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
C.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
D.
sportsAndRecreation
Indicates a relationship where an entity is associated with, involved in, or designated for sports or recreational activities.
-
E.
demonstrationSport
Indicates that an activity is included in an event or program only as a non-medal, exhibition or trial sport rather than as an official competitive discipline.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.