Triple
T28107447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanoi Street Circuit layout (Vietnam Grand Prix) |
E710400
|
entity |
| Predicate | sectionRunsAround |
P52689
|
FINISHED |
| Object | My Dinh National Stadium area |
—
|
NE NERFINISHED |
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: My Dinh National Stadium area | Statement: [Hanoi Street Circuit layout (Vietnam Grand Prix), sectionRunsAround, My Dinh National Stadium area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionRunsAround Context triple: [Hanoi Street Circuit layout (Vietnam Grand Prix), sectionRunsAround, My Dinh National Stadium area]
-
A.
runsAround
chosen
Indicates that one entity moves in a circular or surrounding path around another entity or area.
-
B.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
C.
seDérouleAutourDe
Indicates that an event or process takes place around, centers on, or is organized about a particular entity or theme.
-
D.
runsDirection
Indicates that an entity moves or operates in a specified direction.
-
E.
runsTheLengthOf
Indicates that one entity extends continuously alongside or across the full distance of another entity.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 9:09 p.m.