Triple
T27648209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R1000V |
E696768
|
entity |
| Predicate | dataVendorContext |
P162917
|
FINISHED |
| Object | commonly recognized across major data vendors |
—
|
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: commonly recognized across major data vendors | Statement: [R1000V, dataVendorContext, commonly recognized across major data vendors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataVendorContext Context triple: [R1000V, dataVendorContext, commonly recognized across major data vendors]
-
A.
dataVendor
Indicates a relationship where one entity serves as a provider or supplier of data to another entity.
-
B.
dataVendorName
Indicates the name or identifier of the vendor that supplies or provides the data.
-
C.
dataVendorCategory
Indicates the classification or type category assigned to a data vendor within a defined taxonomy or grouping.
-
D.
dataVendorSymbol
Indicates a mapping between a data vendor and the specific symbol or code they use to identify an asset or item.
-
E.
dataVendorNotation
Indicates that one entity serves as the vendor-specific notation or coding scheme used to represent data defined by another entity.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f631d34c388190bdeb6f523856fc33 |
completed | May 2, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 2:30 p.m.