Triple
T18299051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Icarus |
E438306
|
entity |
| Predicate | destinationClass |
P131248
|
FINISHED |
| Object | nearby stellar systems |
—
|
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 systems | Statement: [Project Icarus, destinationClass, nearby stellar systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationClass Context triple: [Project Icarus, destinationClass, nearby stellar systems]
-
A.
navigationClass
Indicates that one entity serves as a navigation or menu grouping that organizes or links to another entity within a navigational structure.
-
B.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
C.
destinedFor
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
-
D.
designClass
Indicates that one entity is the design or blueprint class from which the other entity is derived or instantiated.
-
E.
positionClass
Indicates the classification or category assigned to an entity based on its role, rank, or position within a defined structure or system.
- F. None of above. chosen
Provenance (4 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017d96588190ac1e326803142976 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.