Triple
T5307249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transformers Metrobase |
E120131
|
entity |
| Predicate | hasImmersionElement |
P63398
|
FINISHED |
| Object | sound effects from Transformers universe |
—
|
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: sound effects from Transformers universe | Statement: [Transformers Metrobase, hasImmersionElement, sound effects from Transformers universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmersionElement Context triple: [Transformers Metrobase, hasImmersionElement, sound effects from Transformers universe]
-
A.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
B.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
C.
hasTopScreenSize
Indicates that an entity (typically a device) possesses a top screen with a specified size or dimension.
-
D.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
-
E.
hasExhibitElement
Indicates that something (such as an exhibit or display) includes or is composed of a particular element or component.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd86f0cbfc8190b6665dd9b28d6345 |
completed | March 20, 2026, 5:42 p.m. |
Created at: March 20, 2026, 1:53 p.m.