Triple
T8288237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gdi32 |
E193832
|
entity |
| Predicate | exportsConcept |
P82547
|
FINISHED |
| Object | device context |
—
|
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: device context | Statement: [Gdi32, exportsConcept, device context]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportsConcept Context triple: [Gdi32, exportsConcept, device context]
-
A.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
B.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
C.
featuredConcept
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
-
D.
isConceptual
Indicates that something exists as an abstract or theoretical idea rather than as a concrete, physical entity.
-
E.
categoryConcept
Indicates that one entity serves as a categorical type or conceptual class under which the other entity is grouped or classified.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c98e15c8190ac2a0b2a5ff834c9 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.