Triple
T16871259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustavus W. Smith |
E421170
|
entity |
| Predicate | dateAsActingCommander |
P125304
|
FINISHED |
| Object | 1862-05-31 |
—
|
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: 1862-05-31 | Statement: [Gustavus W. Smith, dateAsActingCommander, 1862-05-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateAsActingCommander Context triple: [Gustavus W. Smith, dateAsActingCommander, 1862-05-31]
-
A.
appointedAsCommanderInChief
Indicates that an entity is formally assigned the role and authority of commander-in-chief over a specified force, organization, or jurisdiction.
-
B.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
C.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
D.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
E.
startTimeOfPositionHeld_CommandingGeneralOfTheUnitedStatesArmy
Indicates the date and time when an individual began serving in the position of Commanding General of the United States Army.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f1fe5881909b18438d771814e9 |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:29 a.m.