Triple
T14192639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippodrome de Vincennes |
E351749
|
entity |
| Predicate | hasSecondaryTrack |
P3284
|
FINISHED |
| Object | smaller inner track |
—
|
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: smaller inner track | Statement: [Hippodrome de Vincennes, hasSecondaryTrack, smaller inner track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryTrack Context triple: [Hippodrome de Vincennes, hasSecondaryTrack, smaller inner track]
-
A.
hasTwoTracks
Indicates that the subject possesses or is associated with exactly two distinct tracks or pathways.
-
B.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
C.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
D.
hasTrack
chosen
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
E.
hasSecondarySubject
Indicates that an entity is associated with an additional, non-primary subject in a given context or relationship.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61e0a52081908213aa6e548d4418 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:04 a.m.