Triple
T15853026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IDEM |
E384386
|
entity |
| Predicate | hasUnderlying |
P107958
|
FINISHED |
| Object | Italian equities |
—
|
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: Italian equities | Statement: [IDEM, hasUnderlying, Italian equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlying Context triple: [IDEM, hasUnderlying, Italian equities]
-
A.
hasUnderlyingMarket
chosen
Indicates that one entity is based on, derives its value from, or is traded with reference to another entity that serves as its fundamental market.
-
B.
hasUnderlyingEntity
Indicates that one entity serves as the fundamental or base entity upon which another entity is conceptually or structurally built.
-
C.
hasUnderlyingIssuer
Indicates that one entity serves as the fundamental or primary issuer behind another entity, such as a financial instrument or structured product.
-
D.
hasUnderlyingAssets
Indicates that one entity is supported, backed, or derived from another entity or set of entities that serve as its foundational assets.
-
E.
hasUnderlyingSet
Indicates that one mathematical structure is associated with, or based on, a specific underlying set of elements.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:50 a.m.