Triple
T34867450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B-4 |
E1005051
|
entity |
| Predicate | statusAtEndOfNemesis |
P199986
|
FINISHED |
| Object | in Starfleet custody |
—
|
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: in Starfleet custody | Statement: [B-4, statusAtEndOfNemesis, in Starfleet custody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAtEndOfNemesis Context triple: [B-4, statusAtEndOfNemesis, in Starfleet custody]
-
A.
statusAtEndOfFilm
Indicates the condition or situation an entity is in when the film concludes.
-
B.
statusInFinale
Indicates the role, condition, or outcome an entity has specifically in the final episode or concluding segment of a series or event.
-
C.
statusAtRagnarök
Indicates the state or condition an entity is in at the time of Ragnarök.
-
D.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
-
E.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
- F. None of above. chosen
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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
| PDg | Predicate description generation | batch_69ff691e86d0819099fdb5eca5a95632 |
completed | May 9, 2026, 5:04 p.m. |
Created at: May 3, 2026, 4 p.m.