Triple
T6019687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John H. Morgan |
E134032
|
entity |
| Predicate | preWarActivity |
P33336
|
FINISHED |
| Object | Mexican–American War service |
—
|
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: Mexican–American War service | Statement: [John H. Morgan, preWarActivity, Mexican–American War service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preWarActivity Context triple: [John H. Morgan, preWarActivity, Mexican–American War service]
-
A.
prewarActivity
chosen
Indicates activities, conditions, or behaviors that occurred or were carried out before a specific war or armed conflict.
-
B.
preWarCountry
Indicates that a country existed or held a particular status prior to a specified war or major armed conflict.
-
C.
preWarOccupation
Indicates the occupation or role a person held before a specific war or armed conflict.
-
D.
earlyWar
Indicates that the war or conflict occurred in an early phase or at an earlier-than-typical point in a relevant timeline or sequence.
-
E.
preWarServiceArea
Indicates the geographic area or jurisdiction in which an entity operated or provided service before a specified war or conflict.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f86efec8190bc357dddf6ebb4a9 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.