Triple
T28729948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonfly mission |
E730627
|
entity |
| Predicate | plannedArrivalBody |
P175340
|
FINISHED |
| Object | Titan |
—
|
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: Titan | Statement: [Dragonfly mission, plannedArrivalBody, Titan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedArrivalBody Context triple: [Dragonfly mission, plannedArrivalBody, Titan]
-
A.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
B.
arrivalDatePlanned
Indicates the date on which an arrival is scheduled or expected to occur according to a plan.
-
C.
arrivalByShip
Indicates that an entity reaches a destination specifically by traveling on a ship.
-
D.
arrivalFrom
Indicates that an entity arrives at a location or state originating from a specified source location or state.
-
E.
estimatedArrivalInAustralia
Indicates the expected date and/or time when an entity is predicted to arrive in Australia.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 28, 2026, 5:58 a.m.