Triple
T159306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief of the Continental Army |
E3245
|
entity |
| Predicate | startTimeOfSecondTenure |
P1814
|
FINISHED |
| Object | July 3, 1798 |
—
|
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: July 3, 1798 | Statement: [Commander-in-Chief of the Continental Army, startTimeOfSecondTenure, July 3, 1798]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfSecondTenure Context triple: [Commander-in-Chief of the Continental Army, startTimeOfSecondTenure, July 3, 1798]
-
A.
officeHolderStartTime
chosen
Indicates the date and time at which an individual begins holding a particular office or position.
-
B.
vicePresidentialTermEnd
Indicates the date or point in time when an individual's service in a specific vice presidential term comes to an end.
-
C.
primeMinisterTermStart
Indicates the date on which an individual officially begins serving as prime minister.
-
D.
inaugurationDate
Indicates the date on which an official ceremony formally installs a person into a specific office or position.
-
E.
inaugurationYear
Indicates the calendar year in which an entity was formally inaugurated or officially brought into operation.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.