Triple
T34969066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolutions |
E1008483
|
entity |
| Predicate | captainStrandedOnPlanet |
P124624
|
FINISHED |
| Object | Kathryn Janeway |
—
|
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: Kathryn Janeway | Statement: [Resolutions, captainStrandedOnPlanet, Kathryn Janeway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainStrandedOnPlanet Context triple: [Resolutions, captainStrandedOnPlanet, Kathryn Janeway]
-
A.
strandedAfter
Indicates that one entity is left isolated or unable to proceed as a consequence of another entity’s prior action or departure.
-
B.
strandedWith
Indicates that one entity is stuck or left without means to leave in the company or presence of another entity.
-
C.
strandedIn
chosen
Indicates that an entity is left isolated or stuck in a particular place or situation without the means to leave or resolve it.
-
D.
captainDuringExpedition
Indicates that an entity served as the captain of another entity (such as a ship, team, or mission) for the duration of a specific expedition.
-
E.
crashLandedOn
Indicates that one entity made an unintended or uncontrolled landing onto the surface or location represented by another entity.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.