Triple
T16509247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bear clan |
E401012
|
entity |
| Predicate | followsClanInheritance |
P79992
|
FINISHED |
| Object | through mother’s line |
—
|
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: through mother’s line | Statement: [Bear clan, followsClanInheritance, through mother’s line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsClanInheritance Context triple: [Bear clan, followsClanInheritance, through mother’s line]
-
A.
clanInheritance
chosen
Indicates that rights, titles, or property are passed down within a clan according to its internal rules of succession.
-
B.
hasSubclan
Indicates that one clan contains or is composed of a smaller, subordinate clan within its structure.
-
C.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
D.
losesInheritanceThrough
Indicates that one party forfeits or is disqualified from receiving an inheritance as a consequence of another specified party or condition.
-
E.
parentClanChief
Indicates that one entity serves as the clan chief of the parent clan of another entity.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e54331c8190b3c4f9de95cbbc5e |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.