Triple
T83182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isoroku Yamamoto |
E1671
|
entity |
| Predicate | serviceEnd |
P2941
|
FINISHED |
| Object | 1943 |
—
|
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: 1943 | Statement: [Isoroku Yamamoto, serviceEnd, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEnd Context triple: [Isoroku Yamamoto, serviceEnd, 1943]
-
A.
officeEnded
chosen
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
B.
usHouseServiceEnd
Indicates the date or event on which an individual’s service in the U.S. House of Representatives comes to an end.
-
C.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
D.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
E.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24f4ccb5081908decac81f4af01bf |
completed | Feb. 28, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69a24eb469548190b38c24e81f36c838 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.