Triple
T223555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMX |
E4266
|
entity |
| Predicate | componentSelection |
P136
|
FINISHED |
| Object | largest mid-capitalization companies on Euronext Amsterdam |
—
|
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: largest mid-capitalization companies on Euronext Amsterdam | Statement: [AMX, componentSelection, largest mid-capitalization companies on Euronext Amsterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentSelection Context triple: [AMX, componentSelection, largest mid-capitalization companies on Euronext Amsterdam]
-
A.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
B.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
C.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
D.
selectionProcess
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
E.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
- 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.