Triple
T8264566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACE spacecraft |
E193269
|
entity |
| Predicate | hasObserved |
P26705
|
FINISHED |
| Object | coronal mass ejections |
—
|
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: coronal mass ejections | Statement: [ACE spacecraft, hasObserved, coronal mass ejections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObserved Context triple: [ACE spacecraft, hasObserved, coronal mass ejections]
-
A.
hasObservation
chosen
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
B.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
-
C.
isObservedOn
Indicates that a particular phenomenon, condition, or attribute is detected or recorded at a specific time, date, or occasion.
-
D.
hasObserver
Indicates that an entity is being watched, monitored, or examined by another entity acting as an observer.
-
E.
hasSee
Indicates that one entity has perceived or visually observed 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb793aa8f08190b20b3616ceb9bec7 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.