Triple
T37608371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gundrak |
E935716
|
entity |
| Predicate | entranceFactionAccess |
P188376
|
FINISHED |
| Object | Alliance |
—
|
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: Alliance | Statement: [Gundrak, entranceFactionAccess, Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceFactionAccess Context triple: [Gundrak, entranceFactionAccess, Alliance]
-
A.
entranceFaction
chosen
Indicates a relationship where a specific faction controls, guards, or is otherwise associated with an entrance or access point.
-
B.
hasEntranceRole
Indicates that an entity participates in an entrance or access point with a specific functional role or capacity.
-
C.
entranceTrait
Indicates a characteristic or feature associated with how an entity enters or is accessed (e.g., through a particular type or style of entrance).
-
D.
entranceNPC
Indicates that an NPC is positioned at or associated with the entrance of a location, serving as the primary character encountered when entering.
-
E.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.