Triple
T25070562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPE350 |
E627894
|
entity |
| Predicate | hasDataCategory |
P82611
|
FINISHED |
| Object | pricing and index levels |
—
|
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: pricing and index levels | Statement: [SPE350, hasDataCategory, pricing and index levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataCategory Context triple: [SPE350, hasDataCategory, pricing and index levels]
-
A.
hasCategories
chosen
Indicates that an entity is associated with one or more categories that classify or group it.
-
B.
hasRecordCategory
Indicates that something is associated with, or classified under, a particular record category.
-
C.
hasCategoryCount
Indicates the number of distinct categories associated with a given entity.
-
D.
hasDataFields
Indicates that an entity possesses or is associated with specific data fields or attributes.
-
E.
hasCategorySystem
Indicates that an entity is associated with or organized according to a particular categorization system.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:10 a.m.