Triple
T32888593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pathfinder Project |
E841270
|
entity |
| Predicate | firstSuccessfulContactWith |
P58222
|
FINISHED |
| Object | USS Voyager |
E1430327
|
NE 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: USS Voyager | Statement: [Pathfinder Project, firstSuccessfulContactWith, USS Voyager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSuccessfulContactWith Context triple: [Pathfinder Project, firstSuccessfulContactWith, USS Voyager]
-
A.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
B.
firstSuccessfulImpactBy
Indicates that one entity is the earliest or initial successful impactor upon another entity in a given context or sequence of events.
-
C.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
D.
firstMeets
chosen
Indicates that one entity encounters or comes into contact with another entity for the first time.
-
E.
firstContactContext
Indicates the circumstances or situation under which two entities first came into contact or interacted.
- F. None of above.
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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34e4f71da88190abee3cd4d6ef3f89 |
completed | June 19, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:18 a.m.