Triple
T37552509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windrunner |
E933619
|
entity |
| Predicate | familyAlignment |
P193394
|
FINISHED |
| Object | varied alignments across members |
—
|
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: varied alignments across members | Statement: [Windrunner, familyAlignment, varied alignments across members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyAlignment Context triple: [Windrunner, familyAlignment, varied alignments across members]
-
A.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
-
B.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
C.
familyDynamic
Indicates the nature and patterns of interaction, roles, and emotional relationships among members within a family unit.
-
D.
familyIndicator
Indicates that there exists a familial relationship or family-based connection between the referenced entities.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: May 3, 2026, 4:17 p.m.