Triple
T16804026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putnam Competition |
E408431
|
entity |
| Predicate | maximumScore |
P29667
|
FINISHED |
| Object | 120 |
—
|
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: 120 | Statement: [Putnam Competition, maximumScore, 120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumScore Context triple: [Putnam Competition, maximumScore, 120]
-
A.
maximumNumber
chosen
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
B.
corePointsMaximum
Indicates the maximum number of core points that can be assigned, accumulated, or recognized within a given system or context.
-
C.
highestTestScore
Indicates that one entity has achieved the greatest test score among a specified set or in a given context.
-
D.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
E.
maximumEnergy
Indicates the greatest amount of energy that an entity can possess, store, or output under specified conditions.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2ca46f88190b56e81d75012496c |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.