Triple
T16433568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Liver Assurance |
E399126
|
entity |
| Predicate | hasNumberOfMembersAtPeak |
P4549
|
FINISHED |
| Object | over 3 million |
—
|
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 3 million | Statement: [Royal Liver Assurance, hasNumberOfMembersAtPeak, over 3 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfMembersAtPeak Context triple: [Royal Liver Assurance, hasNumberOfMembersAtPeak, over 3 million]
-
A.
memberCountAtPeak
chosen
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
-
B.
numberOfEmployeesAtPeak
Indicates the highest recorded count of employees that an entity had at any point in time.
-
C.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
D.
membershipPeakYear
Indicates the year in which an entity’s membership count reached its highest level.
-
E.
teamCountAtPeak
Indicates the number of team members involved at the highest or peak point of activity, size, or performance.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba01a1c8190b5a4700e2364ae63 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.