Triple
T6638385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lloyd Fredendall |
E150515
|
entity |
| Predicate | laterPromotedTo |
P65413
|
FINISHED |
| Object | lieutenant 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: lieutenant general | Statement: [Lloyd Fredendall, laterPromotedTo, lieutenant general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPromotedTo Context triple: [Lloyd Fredendall, laterPromotedTo, lieutenant general]
-
A.
promotedAt
Indicates the time or date at which an entity was elevated to a higher rank, position, or status.
-
B.
promotedToGeneral
chosen
Indicates that an individual has been elevated in rank to the position or title of general.
-
C.
promotedWithinUnit
Indicates that an individual received a promotion while remaining within the same organizational unit or department.
-
D.
laterPromoter
Indicates that one promoter occurs or becomes active at a later time than another promoter in a regulatory or temporal sequence.
-
E.
laterRaised
Indicates that one entity was raised, elevated, or brought up at a time subsequent to another referenced event or state.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 2 p.m.