Triple
T33328474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union campaigns of 1864 |
E853334
|
entity |
| Predicate | hasStrategicLeader |
P29266
|
FINISHED |
| Object | Ulysses S. Grant |
—
|
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: Ulysses S. Grant | Statement: [Union campaigns of 1864, hasStrategicLeader, Ulysses S. Grant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrategicLeader Context triple: [Union campaigns of 1864, hasStrategicLeader, Ulysses S. Grant]
-
A.
hasStrategicOwner
Indicates that an entity is assigned to and overseen by a specific person or role responsible for its strategic direction and outcomes.
-
B.
hasAlliedLeader
Indicates that one entity serves as an allied leader or commander in relation to another entity.
-
C.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
D.
hasOperationalLeader
Indicates that one entity serves as the person responsible for directing and managing the operations or activities of another entity.
-
E.
chiefStrategist
chosen
Indicates that one entity serves as the primary planner and director of strategy for another entity.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 1, 2026, 1:34 a.m.