Triple
T17149558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice League: Battle for Metropolis |
E416182
|
entity |
| Predicate | interactivityType |
P96076
|
FINISHED |
| Object | shooting gallery |
—
|
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: shooting gallery | Statement: [Justice League: Battle for Metropolis, interactivityType, shooting gallery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactivityType Context triple: [Justice League: Battle for Metropolis, interactivityType, shooting gallery]
-
A.
usedInteractionType
chosen
Indicates the specific type or category of interaction that was used between the related entities.
-
B.
interactiveElement
Indicates that one entity functions as an interface component designed to receive and respond to user actions initiated by another entity.
-
C.
interactive
Indicates that one entity engages in reciprocal or two-way communication or action with another entity.
-
D.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
E.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f4059d90819092d3609326fa3130 |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.