Triple
T634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Medal of Science |
E12
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | medal |
—
|
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: medal | Statement: [National Medal of Science, hasComponent, medal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponent Context triple: [National Medal of Science, hasComponent, medal]
-
A.
hasPart
chosen
Indicates that one entity is a component, segment, or constituent part of another entity.
-
B.
hasRepresentationIn
Indicates that one entity is represented, depicted, or encoded within another entity, such as a concept, object, or data structure having a corresponding representation in a specific medium or context.
-
C.
hasNotableImplementationAt
Indicates that something has a significant or noteworthy implementation located at or associated with a particular place, context, or platform.
-
D.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
E.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
- 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.