Triple
T16927407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baupost Group |
E410610
|
entity |
| Predicate | typicalInvestmentHorizon |
P30772
|
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: [Baupost Group, typicalInvestmentHorizon, long term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInvestmentHorizon Context triple: [Baupost Group, typicalInvestmentHorizon, long term]
-
A.
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.
-
B.
investorObjective
Indicates that an entity’s goal, preference, or intended outcome in its role as an investor is directed toward another entity or investment.
-
C.
timeHorizonOfLoans
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
-
D.
vestmentStyle
Indicates the style or type of clothing or ceremonial garments associated with an entity.
-
E.
investmentScope
Indicates the range or boundaries of activities, assets, or sectors that an investment is intended or allowed to cover.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdf3fc3c8190a884f7ecd5c47adb |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.