Triple
T9115305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Reliant (commandeered) |
E218705
|
entity |
| Predicate | seizedFrom |
P5949
|
FINISHED |
| Object | Starfleet crew of USS Reliant |
—
|
LITERAL 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: Starfleet crew of USS Reliant | Statement: [USS Reliant (commandeered), seizedFrom, Starfleet crew of USS Reliant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seizedFrom Context triple: [USS Reliant (commandeered), seizedFrom, Starfleet crew of USS Reliant]
-
A.
confiscatedBy
chosen
Indicates that something has been taken away and seized by an authority or agent, typically as a legal or disciplinary action.
-
B.
seizedCapital
Indicates that one entity forcibly took control of another entity’s capital city.
-
C.
stolenFrom
Indicates that something was taken unlawfully from a particular source or owner.
-
D.
stolenBy
Indicates that something has been taken unlawfully or without permission by a particular entity.
-
E.
seizedPowerBy
Indicates that one entity took control or authority from another, typically through force, coercion, or other non-consensual means.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a1340881909dc791b825e87ef2 |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.