Triple
T27464443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Chicane |
E693137
|
entity |
| Predicate | isKeySectionFor |
P37831
|
FINISHED |
| Object | race starts and finishes at Le Mans |
—
|
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: race starts and finishes at Le Mans | Statement: [Ford Chicane, isKeySectionFor, race starts and finishes at Le Mans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeySectionFor Context triple: [Ford Chicane, isKeySectionFor, race starts and finishes at Le Mans]
-
A.
hasSectionInKey
Indicates that a key (such as a document, configuration, or data structure key) contains or is associated with a specific section within it.
-
B.
isReferenceSectionFor
Indicates that one entity serves as the reference section or reference part specifically associated with another entity.
-
C.
isNamedSectionOf
Indicates that one entity is a specifically named section or subdivision that forms part of another entity.
-
D.
isOnSectionOf
Indicates that one entity is located on, or positioned along, a specific segment or subsection of another entity.
-
E.
keySection
chosen
Indicates that one section is the primary or most important part within a larger structure or document.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 12:51 p.m.