Triple
T16789577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanguard 2 |
E408069
|
entity |
| Predicate | purposeOfInstrument |
P98789
|
FINISHED |
| Object | detect reflected sunlight from cloud tops |
—
|
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: detect reflected sunlight from cloud tops | Statement: [Vanguard 2, purposeOfInstrument, detect reflected sunlight from cloud tops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfInstrument Context triple: [Vanguard 2, purposeOfInstrument, detect reflected sunlight from cloud tops]
-
A.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
B.
purposeOfGrant
Indicates that a grant is provided with the specific purpose, objective, or intended use described by the associated entity or activity.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
operationalPurpose
chosen
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
-
E.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a50e18819090a30e1f38e520e0 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.