Triple
T24496150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbst Woods |
E617797
|
entity |
| Predicate | notableCommanderInAction |
P126352
|
FINISHED |
| Object | John Buford |
—
|
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: John Buford | Statement: [Herbst Woods, notableCommanderInAction, John Buford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCommanderInAction Context triple: [Herbst Woods, notableCommanderInAction, John Buford]
-
A.
notableCommanderAtAction
chosen
Indicates that a particular commander is notably associated with leading or playing a significant command role in a specific action or event.
-
B.
notableCommanderUnder
Indicates that one entity served as a notable military commander under the authority or leadership of another entity.
-
C.
notableCommanderOf
Indicates that an individual is a distinguished or historically significant commander associated with leading a particular military unit, force, or organization.
-
D.
notableCommanderTried
Indicates that a notable commander made an attempt to perform or achieve the associated action or objective.
-
E.
notableCommanderStart
Indicates the point in time or event at which a notable commander’s leadership or command role begins in relation to the subject.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:22 a.m.