Triple
T4410516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Longshot |
E94840
|
entity |
| Predicate | intendedDestinationType |
P20072
|
FINISHED |
| Object | nearby stellar system |
—
|
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: nearby stellar system | Statement: [Project Longshot, intendedDestinationType, nearby stellar system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedDestinationType Context triple: [Project Longshot, intendedDestinationType, nearby stellar system]
-
A.
servesDestinationType
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
B.
destinedFor
chosen
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
-
C.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
D.
connectsDestinationType
Indicates that one entity serves as a connection or link specifically to a destination of a given type.
-
E.
attemptedDestination
Indicates that an entity made an effort to reach or go to a particular destination, regardless of whether the attempt was successful.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e4c58c8190b4190aad3095a1dd |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.