Triple
T4416120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大田実 |
E94977
|
entity |
| Predicate | 著名な役割 |
P14496
|
FINISHED |
| Object | 沖縄方面根拠地隊司令官 |
—
|
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: 沖縄方面根拠地隊司令官 | Statement: [大田実, 著名な役割, 沖縄方面根拠地隊司令官]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 著名な役割 Context triple: [大田実, 著名な役割, 沖縄方面根拠地隊司令官]
-
A.
hasFamousNamesakeRole
Indicates that an entity has a role or position that shares its name with a well-known or historically notable person.
-
B.
hasMainRole
chosen
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
C.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
-
D.
screenDebutInMajorRoleFor
Indicates that one entity made their first significant on-screen appearance (major role) in a particular production or work.
-
E.
playedKeyRoleIn
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3551afb448190a2ce2000193808ac |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.