Triple
T31911992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massim |
E814710
|
entity |
| Predicate | hasExchangeSystem |
P165684
|
FINISHED |
| Object | Kula ring |
—
|
NE NERFINISHED |
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: Kula ring | Statement: [Massim, hasExchangeSystem, Kula ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExchangeSystem Context triple: [Massim, hasExchangeSystem, Kula ring]
-
A.
hasSecondaryExchange
Indicates that an entity is additionally listed or traded on a secondary exchange beyond its primary market.
-
B.
isExchangedVia
chosen
Indicates that something is transferred or traded from one party to another through a specified medium, channel, or mechanism.
-
C.
hasElectronicTradingSystem
Indicates that an entity operates or utilizes an electronic system for executing trades or transactions.
-
D.
hasFilterExchangeSystem
Indicates that one entity is equipped with or incorporates a system for exchanging or replacing filters.
-
E.
hasFuturesExchange
Indicates that there exists a futures exchange associated with, operated by, or relevant to the referenced entity.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 12:01 a.m.