Triple
T630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Medal of Science |
E12
|
entity |
| Predicate | typicalFrequency |
P85
|
FINISHED |
| Object | annually |
—
|
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: annually | Statement: [National Medal of Science, typicalFrequency, annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFrequency Context triple: [National Medal of Science, typicalFrequency, annually]
-
A.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
-
B.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
C.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
E.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
- 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_69a22735e1b081908bd0457057dcf086 |
completed | Feb. 27, 2026, 11:22 p.m. |
| NER | Named-entity recognition | batch_69a2304aaa2c8190ab7e8dd5da977c11 |
completed | Feb. 28, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69a22918087081909e717b8bee896e8f |
completed | Feb. 27, 2026, 11:30 p.m. |
Created at: Feb. 27, 2026, 11:24 p.m.