Triple
T35469597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reavers |
E1025170
|
entity |
| Predicate | notableShipEncounter |
P129047
|
FINISHED |
| Object | Serenity (Firefly-class transport) |
E2144149
|
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: Serenity (Firefly-class transport) | Statement: [Reavers, notableShipEncounter, Serenity (Firefly-class transport)]
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 (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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a385bc2e2d88190bed5f1c420c0fddf |
completed | June 21, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.