Triple
T6091355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarium Capital |
E135772
|
entity |
| Predicate | knownPeriodOfProminence |
P5250
|
FINISHED |
| Object | 2000s |
—
|
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: 2000s | Statement: [Clarium Capital, knownPeriodOfProminence, 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownPeriodOfProminence Context triple: [Clarium Capital, knownPeriodOfProminence, 2000s]
-
A.
timePeriodOfDominance
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
B.
moreProminentSince
Indicates that one entity has become more prominent or noticeable relative to another entity starting from a specified point in time.
-
C.
eraOfSignificance
chosen
Indicates the historical period or timeframe during which an entity was particularly important, influential, or noteworthy.
-
D.
observationalProminence
Indicates that one entity stands out or is especially noticeable relative to others when observed.
-
E.
timePeriodOfMajorImportance
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057ab7324819086d4708e6f9391c0 |
completed | March 22, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.