Triple
T28050256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NKY |
E708799
|
entity |
| Predicate | hasFieldSuffix |
P34760
|
FINISHED |
| Object | Index (IND) on Bloomberg |
—
|
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: Index (IND) on Bloomberg | Statement: [NKY, hasFieldSuffix, Index (IND) on Bloomberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFieldSuffix Context triple: [NKY, hasFieldSuffix, Index (IND) on Bloomberg]
-
A.
hasNameSuffix
Indicates that an entity’s name includes a specific suffix or ending component.
-
B.
hasFieldName
chosen
Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
-
C.
hasSuffixedRoute
Indicates that a route is a variant or extension of another base route, distinguished by an added suffix in its identifier.
-
D.
hasLetterSuffix
Indicates that an entity’s identifier, name, or code ends with a specific letter or sequence of letters.
-
E.
hasBaseField
Indicates that one entity serves as the foundational or underlying field structure upon which another entity is defined or constructed.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 27, 2026, 8:32 p.m.