Triple
T35469597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reavers |
E1025170
|
entity |
| Predicate | notableShipEncounter |
—
|
GENERATED |
| Object | Serenity (Firefly-class transport) |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShipEncounter Context triple: [Reavers, notableShipEncounter, Serenity (Firefly-class transport)]
-
A.
encountersShip
chosen
Indicates that one entity comes across or meets another ship, typically in the course of travel or movement.
-
B.
notableShipOnRoute
Indicates that a particular ship is especially significant or prominent among those operating on a given route.
-
C.
notableEncounterWith
Indicates that an entity has had a significant or noteworthy meeting, interaction, or confrontation with another entity.
-
D.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
E.
capturedShip
Indicates that one party has taken control of another party's ship, typically by force or seizure.
- F. None of above.
Provenance (1 batch)
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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.