Triple
T3544452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hisaichi Terauchi |
E74960
|
entity |
| Predicate | militaryServiceNumber |
P48795
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [Hisaichi Terauchi, militaryServiceNumber, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryServiceNumber Context triple: [Hisaichi Terauchi, militaryServiceNumber, unknown]
-
A.
airForceServiceNumber
Indicates the unique identification number assigned to an individual for their service in an air force.
-
B.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
C.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
D.
militaryServicePeriod
Indicates the span of time during which an entity serves or has served in a military capacity.
-
E.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
- F. None of above. chosen
Provenance (4 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbf76c5b08190b898d31b80a3a350 |
completed | March 8, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb0a11a1c8190baa8c0eb87ad259a |
completed | March 8, 2026, 5:23 p.m. |
Created at: March 8, 2026, 3:20 p.m.