Triple
T11547563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night Fae |
E273809
|
entity |
| Predicate | roleInShadowlands |
P100066
|
FINISHED |
| Object | shepherds of souls |
—
|
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: shepherds of souls | Statement: [Night Fae, roleInShadowlands, shepherds of souls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInShadowlands Context triple: [Night Fae, roleInShadowlands, shepherds of souls]
-
A.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
B.
roleInTheWrathOfGod
Indicates that an entity has a specific role or participation in the event, concept, or narrative referred to as "the Wrath of God."
-
C.
questRole
Indicates the specific function or part an entity plays within a quest or mission.
-
D.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
-
E.
destinedRole
Indicates that an entity is assigned or fated to fulfill a particular role or function, typically in a future or predetermined context.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822f00a088190ac6b48e45e743899 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.