Triple
T223571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMX |
E4266
|
entity |
| Predicate | dataVendorCodeType |
P2202
|
FINISHED |
| Object | stock index ticker |
—
|
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: stock index ticker | Statement: [AMX, dataVendorCodeType, stock index ticker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataVendorCodeType Context triple: [AMX, dataVendorCodeType, stock index ticker]
-
A.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
B.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
C.
codeType
chosen
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
D.
dealerNetworkCharacteristic
Indicates a characteristic or attribute that describes some aspect of a dealer network.
-
E.
codeshareOperatesFor
Indicates that one airline operates a flight under a codeshare agreement on behalf of another airline, using the latter’s flight number or code.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.