Triple
T38584695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mana-Tombs |
E932319
|
entity |
| Predicate | isPartOfLoreLocation |
P187938
|
FINISHED |
| Object | ruins of Auchindoun |
—
|
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: ruins of Auchindoun | Statement: [Mana-Tombs, isPartOfLoreLocation, ruins of Auchindoun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfLoreLocation Context triple: [Mana-Tombs, isPartOfLoreLocation, ruins of Auchindoun]
-
A.
loreLocation
chosen
Indicates that something is the place or setting where related background story, history, or world-building information is situated or associated.
-
B.
notableGameLocation
Indicates that a particular place is recognized as a significant or prominent location within a game.
-
C.
hasBranchInFictionalLocation
Indicates that an organization maintains a branch, office, or presence within a fictional or imaginary location.
-
D.
fictionalLocationAssociatedWith
Indicates a relationship where a fictional entity (such as a character, event, or work) is connected to or set in a particular fictional location.
-
E.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
- 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_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
Created at: May 3, 2026, 4:32 p.m.