Triple
T7242474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECM |
E156388
|
entity |
| Predicate | predictionHorizon |
P75972
|
FINISHED |
| Object | long-term |
—
|
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: long-term | Statement: [ECM, predictionHorizon, long-term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predictionHorizon Context triple: [ECM, predictionHorizon, long-term]
-
A.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
B.
foreseesImplementationPeriodOf
Indicates that one entity anticipates or plans the future time frame during which another entity will be implemented or carried out.
-
C.
forecastUsing
Indicates that one entity generates or derives a forecast by using information, methods, or data from another entity.
-
D.
metProphet
Indicates that one entity has personally encountered or come into direct contact with the prophet.
-
E.
goalHorizon
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
- F. None of above. chosen
Provenance (4 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea56756c8190996c2390902f166a |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6ea539f5c81908001524149903559 |
completed | March 27, 2026, 8:36 p.m. |
Created at: March 27, 2026, 2:55 p.m.