Triple
T14067184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lake |
E338504
|
entity |
| Predicate | promotedToGeneralYear |
P65413
|
FINISHED |
| Object | 1802 |
—
|
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: 1802 | Statement: [Lord Lake, promotedToGeneralYear, 1802]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedToGeneralYear Context triple: [Lord Lake, promotedToGeneralYear, 1802]
-
A.
promotedToGeneral
chosen
Indicates that an individual has been elevated in rank to the position or title of general.
-
B.
promotedToMajorGeneralOfVolunteers
Indicates that a person was elevated in rank to serve as a major general within a volunteer military force.
-
C.
ordinationYear
Indicates the year in which an individual was formally ordained to a religious office or role.
-
D.
promotedToMajorGeneralCSA
Indicates that a person was elevated in rank to become a major general in the Confederate States Army.
-
E.
promotedToRankBy
Indicates that an entity was elevated to a particular rank or position through the action or decision of 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568b81f08190a571004261c0e8e4 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.