Triple
T10918847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hårga |
E257890
|
entity |
| Predicate | outsiderRole |
P45873
|
FINISHED |
| Object | visitors used as ritual sacrifices |
—
|
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: visitors used as ritual sacrifices | Statement: [Hårga, outsiderRole, visitors used as ritual sacrifices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outsiderRole Context triple: [Hårga, outsiderRole, visitors used as ritual sacrifices]
-
A.
externalRole
chosen
Indicates that an entity holds a role or position in relation to another entity or organization that is outside its primary or internal structure.
-
B.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
C.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
-
D.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
-
E.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77080317881909fc50ac3576cefa8 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.