Triple
T14418054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuwait national development plan |
E357507
|
entity |
| Predicate | hasLongTermHorizon |
P38657
|
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: [Kuwait national development plan, hasLongTermHorizon, long-term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongTermHorizon Context triple: [Kuwait national development plan, hasLongTermHorizon, long-term]
-
A.
goalHorizon
chosen
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
B.
investmentHorizon
Indicates the typical time period over which an investment is expected to be held before its goals are evaluated or the capital is withdrawn.
-
C.
timeHorizonCovered
Indicates the span or duration of time that is encompassed or addressed by something (such as a plan, forecast, or agreement).
-
D.
timeHorizonOfLoans
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
-
E.
hasLongerRepaymentTermThan
Indicates that the repayment term of one entity (e.g., a loan or debt) is longer in duration than the repayment term of another 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cec8e4819087c72d82f9caacda |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:17 a.m.