Triple
T185084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEX index |
E3962
|
entity |
| Predicate | dataVendorCode |
P508
|
FINISHED |
| Object | ^AEX |
—
|
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: ^AEX | Statement: [AEX index, dataVendorCode, ^AEX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataVendorCode Context triple: [AEX index, dataVendorCode, ^AEX]
-
A.
numericCode
chosen
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
B.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
C.
businessPartner
Indicates a formal collaborative relationship between two entities that work together in a business context, typically sharing responsibilities, risks, or benefits.
-
D.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
E.
distributor
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2592867108190b5d316c055575449 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.