Triple
T33658220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cofunds |
E862279
|
entity |
| Predicate | assetsUnderAdministrationPeak |
P177179
|
FINISHED |
| Object | over £70 billion |
—
|
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: over £70 billion | Statement: [Cofunds, assetsUnderAdministrationPeak, over £70 billion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assetsUnderAdministrationPeak Context triple: [Cofunds, assetsUnderAdministrationPeak, over £70 billion]
-
A.
deploymentPeakNumber
Indicates the maximum number of deployments (or deployment instances) reached during a specified period or under given conditions.
-
B.
operatorAtPeak
Indicates that an operator is present and performing their role at the peak or highest point of a process, structure, or operational cycle.
-
C.
hasNumberAtPeak
Indicates that an entity possesses a specific numerical value measured at its highest or peak point.
-
D.
reachedPeakUnder
Indicates that an entity achieved its highest level of success, performance, or influence during the tenure or leadership period of another entity.
-
E.
numberOfEmployeesAtPeak
Indicates the highest recorded count of employees that an entity had at any point in time.
- F. None of above. chosen
Provenance (4 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:42 a.m.