Triple
T12425405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anabasis Investments |
E296884
|
entity |
| Predicate | eraOfNotableActivity |
P24496
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Anabasis Investments, eraOfNotableActivity, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfNotableActivity Context triple: [Anabasis Investments, eraOfNotableActivity, 1980s]
-
A.
notableYearOfActivity
Indicates the specific year during which an entity was particularly active, prominent, or notable in its activities or impact.
-
B.
eraOfHonouredPersonActivity
Indicates the historical period or era during which the honoured person carried out their notable activities.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableDeed
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
E.
wasProminentIn
chosen
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.