Triple
T38590994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hrothgar |
E932451
|
entity |
| Predicate | clanHelionsLoyalTo |
P1915
|
FINISHED |
| Object | a single queen |
—
|
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: a single queen | Statement: [Hrothgar, clanHelionsLoyalTo, a single queen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanHelionsLoyalTo Context triple: [Hrothgar, clanHelionsLoyalTo, a single queen]
-
A.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
B.
clanFamilyOf
Indicates that one entity belongs to, descends from, or is otherwise affiliated with the same clan or extended family group as another entity.
-
C.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
D.
clanCrestAssociatedWith
Indicates that a particular clan crest is symbolically or traditionally linked to a specific clan or family.
-
E.
associatedClan
chosen
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.