Triple
T13084314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSPTSE |
E310290
|
entity |
| Predicate | dataVendorNotation |
P107959
|
FINISHED |
| Object | index symbol |
—
|
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: index symbol | Statement: [GSPTSE, dataVendorNotation, index symbol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataVendorNotation Context triple: [GSPTSE, dataVendorNotation, index symbol]
-
A.
dataVendorSymbol
Indicates a mapping between a data vendor and the specific symbol or code they use to identify an asset or item.
-
B.
dataVendor
Indicates a relationship where one entity serves as a provider or supplier of data to another entity.
-
C.
dataVendorName
Indicates the name or identifier of the vendor that supplies or provides the data.
-
D.
dataVendorSymbolType
Indicates the type or category of symbol used by a particular data vendor to identify an instrument or entity.
-
E.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:02 p.m.