Triple
T36485601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus External Payload Facility |
E898924
|
entity |
| Predicate | hasHostedPayload |
P113543
|
FINISHED |
| Object | Solar Monitoring Observatory (SOLAR) |
—
|
NE NERFINISHED |
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: Solar Monitoring Observatory (SOLAR) | Statement: [Columbus External Payload Facility, hasHostedPayload, Solar Monitoring Observatory (SOLAR)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostedPayload Context triple: [Columbus External Payload Facility, hasHostedPayload, Solar Monitoring Observatory (SOLAR)]
-
A.
hasBeenHostedIn
Indicates that an event, show, or activity took place or was conducted at a particular location or venue in the past.
-
B.
hasPayload
Indicates that one entity carries, contains, or is equipped with another entity as its payload.
-
C.
hasHosts
chosen
Indicates that one entity serves as the host or hosting environment for another entity.
-
D.
hasFormerHost
Indicates that an entity previously served as the host of another entity but no longer holds that hosting role.
-
E.
hasHostedSport
Indicates that a place or organization has served as the venue or organizer for one or more sporting events.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:10 p.m.