Triple
T7969309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doom Buggy |
E185283
|
entity |
| Predicate | audioSystem |
P70173
|
FINISHED |
| Object | individual speaker system per vehicle |
—
|
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: individual speaker system per vehicle | Statement: [Doom Buggy, audioSystem, individual speaker system per vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioSystem Context triple: [Doom Buggy, audioSystem, individual speaker system per vehicle]
-
A.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
B.
soundHardware
Indicates that an entity is associated with, uses, or provides sound-related hardware components or capabilities.
-
C.
usesSoundDevice
Indicates that one entity operates or relies on a sound-producing or sound-processing device in relation to another entity or context.
-
D.
soundReproductionMethod
Indicates the method or technique used to reproduce or play back sound.
-
E.
hasSoundSystem
chosen
Indicates that an entity is equipped with or includes a sound system as one of its features.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd1c9a081909759e5bf5237204e |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.