Triple
T14013306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Compensation Commission |
E337140
|
entity |
| Predicate | numberOfClaimsProcessed |
P77770
|
FINISHED |
| Object | millions of claims (approximate) |
—
|
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: millions of claims (approximate) | Statement: [United Nations Compensation Commission, numberOfClaimsProcessed, millions of claims (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfClaimsProcessed Context triple: [United Nations Compensation Commission, numberOfClaimsProcessed, millions of claims (approximate)]
-
A.
numberOfClaimants
Indicates the quantity of individuals or parties making a claim in a given context or case.
-
B.
totalCustomerClaimsFiled
chosen
Indicates the total number of claims that have been filed by customers.
-
C.
statusForMostNewClaimants
Indicates the status condition that applies to the majority of individuals who are newly making claims.
-
D.
yearClaimsSold
Indicates the specific year in which the claims were sold.
-
E.
numberOfCharges
Indicates the count of distinct charges, accusations, or fee items associated with an entity or event.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f37d11481909159bdb9e1e8d38e |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.