Triple
T165816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacArthur Fellows |
E3012
|
entity |
| Predicate | payoutDuration |
P302
|
FINISHED |
| Object | over five years |
—
|
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 five years | Statement: [MacArthur Fellows, payoutDuration, over five years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payoutDuration Context triple: [MacArthur Fellows, payoutDuration, over five years]
-
A.
commitmentTiming
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
-
B.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
-
C.
settlementPattern
Indicates how human dwellings or communities are spatially arranged and distributed across a geographic area.
-
D.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
deliveryGuarantee
Indicates that one party commits to ensuring that an item, service, or outcome will be delivered under specified conditions or within a defined timeframe.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a25883ac8481909616b2179561bd98 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25664ba8081908ac298511a9fc5ba |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.