Triple

T15834642
Position Surface form Disambiguated ID Type / Status
Subject SAE Combo E383954 entity
Predicate usesCommunicationStandard P34297 FINISHED
Object ISO 15118 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: ISO 15118 | Statement: [SAE Combo, usesCommunicationStandard, ISO 15118]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCommunicationStandard
Context triple: [SAE Combo, usesCommunicationStandard, ISO 15118]
  • A. usedToCommunicate
    Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
  • B. usesTelecommunications
    Indicates that one entity communicates with or transmits information to another by means of telecommunications technologies or networks.
  • C. communicationCapability
    Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
  • D. hasCommunicationInterface chosen
    Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
  • E. enablesCommunicationWith
    Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e11e673e08819080c3f55a225607c7 completed April 16, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69e005418f588190824d91ff7974dada completed April 15, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:49 a.m.