Triple
T21685213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 寺内正照 |
E535211
|
entity |
| Predicate | 親族関係 |
P89441
|
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.
politicalRelationship
Indicates a relationship in which entities are connected through political roles, alliances, affiliations, or interactions within a political context.
-
B.
familyConnectionTo
chosen
Indicates a familial relationship or bond that exists between two entities, such as by blood, marriage, or adoption.
-
C.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
D.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
E.
kinshipNetwork
Indicates a familial relationship structure connecting individuals through blood, marriage, or adoption within a broader family network.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96ca668481909f53853c7a8ea811 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.