Triple
T15755053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTSEMIB |
E381945
|
entity |
| Predicate | isRealTimeCalculated |
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: [FTSEMIB, isRealTimeCalculated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRealTimeCalculated Context triple: [FTSEMIB, isRealTimeCalculated, 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.
calculationTime
Indicates the amount of time required to perform or complete a calculation.
-
D.
calculatedOn
Indicates that a value, result, or outcome is computed based on or using the referenced entity as its input, basis, or context.
-
E.
supportsRealTimeMonitoring
Indicates that an entity provides the capability to observe and track relevant data or events continuously as they occur in real time.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05031f6a08190bfb333eced0a59a1 |
completed | April 16, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.