Triple
T38479209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J200 |
E915623
|
entity |
| Predicate | hasUnderlyingType |
P128043
|
FINISHED |
| Object | equity index |
—
|
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: equity index | Statement: [J200, hasUnderlyingType, equity index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingType Context triple: [J200, hasUnderlyingType, equity index]
-
A.
hasUnderlyingEntity
Indicates that one entity serves as the fundamental or base entity upon which another entity is conceptually or structurally built.
-
B.
hasUnderlyingSet
Indicates that one mathematical structure is associated with, or based on, a specific underlying set of elements.
-
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.
hasRootType
Indicates that an entity possesses or is associated with a primary or fundamental type that serves as its root classification.
-
E.
hasAssociatedType
chosen
Indicates that one entity is linked to another entity that specifies its type, category, or classification.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:31 p.m.