Triple
T22918298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP |
E568789
|
entity |
| Predicate | dataProviderSymbolFormat |
P149332
|
FINISHED |
| Object | NASDAQ:PEP |
—
|
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: NASDAQ:PEP | Statement: [PEP, dataProviderSymbolFormat, NASDAQ:PEP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataProviderSymbolFormat Context triple: [PEP, dataProviderSymbolFormat, NASDAQ:PEP]
-
A.
valueFormatExample
Indicates an example of how a value should be formatted or represented.
-
B.
selectionFormat
Indicates the specific structure or style in which a selection or choice is represented or presented.
-
C.
hasFormatSpecification
Indicates that something is associated with a particular format definition or specification that describes how it should be structured or represented.
-
D.
coordinateFormat
Indicates the specific representation or notation used to express a set of coordinates.
-
E.
markerFormat
chosen
Indicates the specific style or format in which a marker (such as a symbol, label, or annotation) is presented or rendered in relation to something it marks.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807b254c8190bb84596dcacaa35e |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.