Triple
T28521472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burt |
E721780
|
entity |
| Predicate | drivesThrough |
P246
|
FINISHED |
| Object | cornfields near Gatlin |
—
|
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: cornfields near Gatlin | Statement: [Burt, drivesThrough, cornfields near Gatlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivesThrough Context triple: [Burt, drivesThrough, cornfields near Gatlin]
-
A.
drivesOn
chosen
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
B.
drives
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
-
C.
drivesMad
Indicates that one entity causes another entity to become extremely annoyed, frustrated, or mentally unsettled.
-
D.
drivingChallenge
Indicates a situation in which driving is made difficult or demanding due to conditions, obstacles, or required skills.
-
E.
droveFor
Indicates that one entity operated a vehicle on behalf of, or in service to, another entity for a certain period or purpose.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:21 a.m.