Triple
T38345171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Himiko |
E1041518
|
entity |
| Predicate | fatherCharacterHealthStatus |
P143342
|
FINISHED |
| Object | terminally ill |
—
|
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: terminally ill | Statement: [House of Himiko, fatherCharacterHealthStatus, terminally ill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatherCharacterHealthStatus Context triple: [House of Himiko, fatherCharacterHealthStatus, terminally ill]
-
A.
fatherStatus
Indicates that one entity holds the role or status of being a father in relation to another entity.
-
B.
patriarchCharacterStatus
Indicates that a character holds the role or status of a patriarch within a family, group, or lineage.
-
C.
fatherCondition
chosen
Indicates a condition, state, or requirement specifically associated with the father in a given relationship or context.
-
D.
fatherPosition
Indicates the spatial or positional relationship occupied by a father relative to another referenced entity or location.
-
E.
fatherWas
Indicates that one entity was the male parent (father) of another entity in the past.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.