Triple
T36744258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maeglin |
E907708
|
entity |
| Predicate | childOfMixedKindreds |
P187018
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Maeglin, childOfMixedKindreds, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: childOfMixedKindreds Context triple: [Maeglin, childOfMixedKindreds, true]
-
A.
choseKindredOf
Indicates that one entity selected or designated another entity as a kindred, ally, or closely affiliated counterpart.
-
B.
illegitimateChildOf
Indicates that one person is the child of another, but the parent–child relationship is not recognized as lawful or legitimate under the relevant social or legal norms.
-
C.
intendedFamily
Indicates that one entity is planned or designated to be part of another entity’s family or familial group in the future.
-
D.
consideredDaughterOf
Indicates that one entity is regarded or treated as the daughter of another entity, whether by biology, law, or social recognition.
-
E.
grandchildren
Indicates a familial relationship where one entity is the child of another entity’s child.
- F. None of above. chosen
Provenance (4 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.