Triple
T4879035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiʻiaka |
E109278
|
entity |
| Predicate | hasDiscoveryMethod |
P7311
|
FINISHED |
| Object | optical telescope observations |
—
|
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: optical telescope observations | Statement: [Hiʻiaka, hasDiscoveryMethod, optical telescope observations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscoveryMethod Context triple: [Hiʻiaka, hasDiscoveryMethod, optical telescope observations]
-
A.
hasDiscovered
Indicates that one entity has found, detected, or uncovered the existence, presence, or truth of another entity or phenomenon.
-
B.
hasDiscoveryStatus
Indicates the current state or phase of discovery or identification associated with an entity.
-
C.
hasDiscoveryFacility
Indicates that an entity has, is associated with, or is served by a facility where discoveries (such as scientific, medical, or technological findings) are made or were made.
-
D.
discoveryMethod
chosen
Indicates the process, technique, or approach by which something was found, detected, or identified.
-
E.
hasDiscoveryPeriod
Indicates the time span during which a particular discovery was made or recognized.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbf37ac819085bb758bc6406271 |
completed | March 20, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.