Triple
T15884708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunichi Mikawa |
E385160
|
entity |
| Predicate | militaryCareerStart |
P19194
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Gunichi Mikawa, militaryCareerStart, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCareerStart Context triple: [Gunichi Mikawa, militaryCareerStart, early 20th century]
-
A.
hasMilitaryServiceStart
chosen
Indicates the date or point in time when an entity’s period of military service began.
-
B.
militaryServicePeriod
Indicates the span of time during which an entity serves or has served in a military capacity.
-
C.
militaryBackground
Indicates that an entity has prior or current experience, service, or training in a military organization.
-
D.
mainCharacterMilitaryService
Indicates that the main character has served or is serving in the military, capturing their involvement in formal armed forces service.
-
E.
postMilitaryCareer
Indicates that one entity’s career or occupation occurs after the completion of their military service.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.