Triple
T38589143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lower Spire |
E932412
|
entity |
| Predicate | containsEncounterType |
P203906
|
FINISHED |
| Object | single-target boss fights |
—
|
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: single-target boss fights | Statement: [The Lower Spire, containsEncounterType, single-target boss fights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEncounterType Context triple: [The Lower Spire, containsEncounterType, single-target boss fights]
-
A.
hasEncounter
Indicates that one entity experiences or comes into contact with another entity or event, typically in a specific context or situation.
-
B.
followsEncounter
Indicates that one encounter occurs after and in sequence with another encounter.
-
C.
encounterID
Indicates a unique identifier that links all data and events associated with a single encounter or interaction between entities.
-
D.
teamRoleInEncounters
Indicates the specific role an entity holds within a team during particular encounters or interactions.
-
E.
encounterOrder
Indicates the sequence in which entities meet or come into contact with each other.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_6a024936acc48190bc4a9abe4c519302 |
completed | May 11, 2026, 9:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.