Triple
T18098682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YellaWood 500 |
E433155
|
entity |
| Predicate | trackBanking |
P130414
|
FINISHED |
| Object | high-banked oval |
—
|
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: high-banked oval | Statement: [YellaWood 500, trackBanking, high-banked oval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackBanking Context triple: [YellaWood 500, trackBanking, high-banked oval]
-
A.
banksOften
Indicates that the subject frequently or habitually engages in banking activities with the object (such as depositing, withdrawing, or otherwise using banking services).
-
B.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
-
C.
turnBanking
Indicates that an entity is executing a turning maneuver that involves banking or tilting laterally, typically as part of directional change.
-
D.
bank
Indicates that an entity provides financial services such as holding deposits, lending money, or managing financial transactions for another entity.
-
E.
servesBank
Indicates that one entity provides banking or financial services to another entity.
- F. None of above. chosen
Provenance (4 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb3ef548190a322f98917b54a59 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:27 a.m.