Triple
T38464469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinstripe Potoroo |
E912528
|
entity |
| Predicate | bossStage |
P126648
|
FINISHED |
| Object | Pinstripe Potoroo boss battle |
—
|
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: Pinstripe Potoroo boss battle | Statement: [Pinstripe Potoroo, bossStage, Pinstripe Potoroo boss battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossStage Context triple: [Pinstripe Potoroo, bossStage, Pinstripe Potoroo boss battle]
-
A.
goalStage
Indicates the specific phase or step a goal is currently in within its overall progression or lifecycle.
-
B.
stageBossOf
chosen
Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with another entity.
-
C.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
-
D.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
E.
coreStageType
Indicates the specific kind or classification of a core stage within a larger process, system, or lifecycle.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.