Triple
T2926029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathaniel Lyon |
E78845
|
entity |
| Predicate | appointedBrigadierGeneral |
P43971
|
FINISHED |
| Object | 1861-05 |
—
|
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: 1861-05 | Statement: [Nathaniel Lyon, appointedBrigadierGeneral, 1861-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedBrigadierGeneral Context triple: [Nathaniel Lyon, appointedBrigadierGeneral, 1861-05]
-
A.
promotedToViceAdmiral
Indicates that an entity has been elevated in rank or position to the role of Vice Admiral.
-
B.
appointedFrom
Indicates that an entity was selected or assigned to a position or role originating from a specified source, body, or prior position.
-
C.
chiefOfStaff
Indicates that one entity serves as the chief of staff for another entity, typically managing operations and coordinating activities on its behalf.
-
D.
promotedToAdmiral
Indicates that an entity has been elevated in rank or position to the status of admiral.
-
E.
warSecretary
Indicates that one entity serves as the war secretary (or secretary of war/defense) of another entity, typically a government or state.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:55 p.m.