Triple
T33030148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillaume d’Orange epic cycle |
E845141
|
entity |
| Predicate | heroFamily |
P28764
|
FINISHED |
| Object | Aymeri de Narbonne’s lineage |
—
|
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: Aymeri de Narbonne’s lineage | Statement: [Guillaume d’Orange epic cycle, heroFamily, Aymeri de Narbonne’s lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroFamily Context triple: [Guillaume d’Orange epic cycle, heroFamily, Aymeri de Narbonne’s lineage]
-
A.
enemyFamily
Indicates that two entities belong to families that are hostile or in conflict with each other.
-
B.
topFamily
Indicates that the subject entity belongs to the highest-ranking or primary family group within a given hierarchy or classification.
-
C.
familyOf
chosen
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
E.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.