Triple
T1966117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reebok Human Rights Award |
E42690
|
entity |
| Predicate | typicalAwardeesNumberPerYear |
P1620
|
FINISHED |
| Object | several individuals |
—
|
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: several individuals | Statement: [Reebok Human Rights Award, typicalAwardeesNumberPerYear, several individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAwardeesNumberPerYear Context triple: [Reebok Human Rights Award, typicalAwardeesNumberPerYear, several individuals]
-
A.
typicalNumberOfLaureatesPerYear
chosen
Indicates the usual or average number of laureates associated with a given award or context in a single year.
-
B.
typicalNumberOfLaureatesPerCycle
Indicates the usual or average number of laureates associated with each award cycle or iteration.
-
C.
maximumNumberOfLaureatesPerYear
Indicates the highest allowable or observed count of laureates associated with a given year.
-
D.
typicalAwardAmount
Indicates the usual or most common amount of an award given in this relationship.
-
E.
typicalAwardDate
Indicates the date on which an award is customarily or normally given or conferred.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3cd47388190998b5f6800141c92 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.