Triple
T29833622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seth M. Barton |
E757593
|
entity |
| Predicate | notableRankDate |
P925
|
FINISHED |
| Object | promoted brigadier general in 1862 |
—
|
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: promoted brigadier general in 1862 | Statement: [Seth M. Barton, notableRankDate, promoted brigadier general in 1862]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRankDate Context triple: [Seth M. Barton, notableRankDate, promoted brigadier general in 1862]
-
A.
notableRank
Indicates that an entity holds a distinguished or significant position or level within a ranking or hierarchy.
-
B.
notableRaceDate
Indicates that a specific date is recognized as significant or noteworthy for a particular race event.
-
C.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
D.
notableOperationDate
Indicates the date on which a significant or noteworthy operation, event, or activity associated with an entity took place.
-
E.
hasNotableRanking
Indicates that an entity holds a significant or distinguished position within an ordered list or ranking system.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:35 p.m.