Triple
T2919547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P/TSX Composite Index |
E78685
|
entity |
| Predicate | calculatedInRealTime |
P27896
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [S&P/TSX Composite Index, calculatedInRealTime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calculatedInRealTime Context triple: [S&P/TSX Composite Index, calculatedInRealTime, true]
-
A.
isCalculatedInRealTime
chosen
Indicates that the value or result is computed dynamically at the moment of use rather than being precomputed or stored.
-
B.
hasRealTimeInformation
Indicates that up-to-date, continuously refreshed information is available about the related entity or event.
-
C.
calibratedFor
Indicates that something has been adjusted or tuned to operate accurately or optimally for a specific target, condition, or context.
-
D.
realityStatus
Indicates the relationship between an entity and its state of existence or authenticity within a given context or world (e.g., real, fictional, hypothetical, simulated).
-
E.
supportsRealTimePresence
Indicates that an entity provides or enables real-time awareness of other users’ current status, activity, or availability.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:54 p.m.