Triple
T2839511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariel Investments |
E62429
|
entity |
| Predicate | timeHorizonFocus |
P30772
|
FINISHED |
| Object | multi-year investment horizon |
—
|
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: multi-year investment horizon | Statement: [Ariel Investments, timeHorizonFocus, multi-year investment horizon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeHorizonFocus Context triple: [Ariel Investments, timeHorizonFocus, multi-year investment horizon]
-
A.
goalHorizon
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
B.
timePerspective
Indicates how an entity conceptually relates to or orients itself toward time, such as focusing on past, present, or future.
-
C.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
D.
investmentHorizon
chosen
Indicates the typical time period over which an investment is expected to be held before its goals are evaluated or the capital is withdrawn.
-
E.
timeHorizonOfLoans
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdef145f08190be8556bc696ba3ab |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.