Triple
T36635864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SET Index |
E904460
|
entity |
| Predicate | hasRelatedIndex |
P204978
|
FINISHED |
| Object | SET50 Index |
E904461
|
NE 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: SET50 Index | Statement: [SET Index, hasRelatedIndex, SET50 Index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedIndex Context triple: [SET Index, hasRelatedIndex, SET50 Index]
-
A.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
B.
hasIndexes
Indicates that an entity possesses one or more index structures or references used for organizing, locating, or accessing its associated data or elements.
-
C.
hasRelatedField
Indicates that one field is associated with or connected to another field in a relevant or contextually meaningful way.
-
D.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
E.
hasRelatedResult
Indicates that one entity has an associated outcome, effect, or result that is meaningfully connected to it.
- F. None of above. chosen
Provenance (5 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a3814ab588190bd0d786587cb0fc2 |
completed | June 23, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.