Triple
T37472458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanguine Depths |
E931186
|
entity |
| Predicate | ownerFactionInLore |
P136898
|
FINISHED |
| Object | Stone Legion |
—
|
NE NERFINISHED |
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: Stone Legion | Statement: [Sanguine Depths, ownerFactionInLore, Stone Legion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerFactionInLore Context triple: [Sanguine Depths, ownerFactionInLore, Stone Legion]
-
A.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
B.
associatedWithDynastyOrFaction
chosen
Indicates that an entity is linked to, belongs to, or is significantly connected with a particular dynasty or faction.
-
C.
ownerInMyth
Indicates that one entity is the mythological owner, possessor, or master of another entity within a myth or legend.
-
D.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
-
E.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:17 p.m.