Triple
T34056955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boone’s Trace |
E873386
|
entity |
| Predicate | blazedBy |
P178183
|
FINISHED |
| Object | Daniel Boone |
—
|
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: Daniel Boone | Statement: [Boone’s Trace, blazedBy, Daniel Boone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blazedBy Context triple: [Boone’s Trace, blazedBy, Daniel Boone]
-
A.
blowsOver
Indicates that one entity is toppled or knocked down by the force or movement of another entity.
-
B.
laterBlownUpTo
Indicates that one entity is subsequently destroyed or blown up at a later time relative to another referenced event or state.
-
C.
blindedBy
Indicates that one entity causes another to lose the ability to see or perceive clearly, either literally or metaphorically.
-
D.
trailblazerFor
Indicates that one entity serves as a pioneering example, opening the way or setting a precedent for another entity to follow or build upon.
-
E.
blowsAcross
Indicates that something (typically wind, air, or a current) moves across or over another entity or area, passing from one side or region to another.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:52 a.m.