Triple
T3429340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moto |
E72299
|
entity |
| Predicate | communicationTechnology |
P3332
|
FINISHED |
| Object | 4G LTE |
—
|
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: 4G LTE | Statement: [Moto, communicationTechnology, 4G LTE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationTechnology Context triple: [Moto, communicationTechnology, 4G LTE]
-
A.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
B.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
C.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
-
D.
communicationMode
chosen
Indicates the method or channel through which communication between entities is carried out.
-
E.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9854ca081909e637adcac46a27c |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.