Triple
T37974631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Orkney |
E947386
|
entity |
| Predicate | memberOfFaction |
P106973
|
FINISHED |
| Object | northern kings in Arthurian legend |
—
|
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: northern kings in Arthurian legend | Statement: [House of Orkney, memberOfFaction, northern kings in Arthurian legend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfFaction Context triple: [House of Orkney, memberOfFaction, northern kings in Arthurian legend]
-
A.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
B.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
-
C.
factionAssociated
chosen
Indicates that an entity is connected to, aligned with, or belongs to a particular faction.
-
D.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
E.
commanderAffiliation
Indicates that a commander is formally associated with, belongs to, or serves under a particular organization, group, or side.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:20 p.m.