Triple
T37897226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Niuzao Temple |
E945312
|
entity |
| Predicate | supportsQueueSystem |
P13398
|
FINISHED |
| Object | Dungeon Finder |
E2232991
|
NE 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: Dungeon Finder | Statement: [Siege of Niuzao Temple, supportsQueueSystem, Dungeon Finder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsQueueSystem Context triple: [Siege of Niuzao Temple, supportsQueueSystem, Dungeon Finder]
-
A.
usesQueue
Indicates that one entity employs or relies on a queue mechanism to manage or process items, tasks, or messages.
-
B.
usesVirtualQueueSystem
Indicates that an entity manages access or service order through a virtual queuing mechanism rather than a traditional physical line.
-
C.
supportsBrigade
Indicates that one entity provides assistance, resources, or backing to a brigade in carrying out its functions or operations.
-
D.
supportedSystem
chosen
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
E.
hasQueue
Indicates that an entity maintains or is associated with a queue, typically representing an ordered list of items or tasks awaiting processing.
- F. None of above.
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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41043e22a88190ab6aab3ec60808ae |
completed | June 28, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.