Triple
T11640598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor’s Northern Mexico campaign |
E276647
|
entity |
| Predicate | leadCommanderRank |
P30999
|
FINISHED |
| Object | Major General |
—
|
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: Major General | Statement: [Taylor’s Northern Mexico campaign, leadCommanderRank, Major General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadCommanderRank Context triple: [Taylor’s Northern Mexico campaign, leadCommanderRank, Major General]
-
A.
hasCommanderRank
chosen
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
B.
commanderInChiefRank
Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
-
C.
governmentCommanderRank
Indicates that an individual holds a specific rank within a government’s command or leadership hierarchy.
-
D.
airCommanderRank
Indicates that one entity holds the rank or position of air commander relative to another entity (such as a force, unit, or operation).
-
E.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a260ab488190ab1c00d9850f3096 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.