Triple
T38061054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mechagon City |
E950339
|
entity |
| Predicate | bossEncountersInclude |
P86453
|
FINISHED |
| Object | King Mechagon |
—
|
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: King Mechagon | Statement: [Mechagon City, bossEncountersInclude, King Mechagon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossEncountersInclude Context triple: [Mechagon City, bossEncountersInclude, King Mechagon]
-
A.
raidBossIn
Indicates that an entity serves as or is designated as the raid boss within a specified raid, instance, or location.
-
B.
hasBossFights
chosen
Indicates that something (such as a game, level, or scenario) includes one or more boss battles against especially powerful opponents.
-
C.
optionalBoss
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
-
D.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
-
E.
numberOfBosses
Indicates the count of distinct boss or supervisor entities associated with a given entity.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.