Triple
T35261829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nomad begins altering Enterprise systems |
E1018388
|
entity |
| Predicate | occursOnStarship |
P183179
|
FINISHED |
| Object | USS Enterprise (NCC-1701) |
—
|
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: USS Enterprise (NCC-1701) | Statement: [Nomad begins altering Enterprise systems, occursOnStarship, USS Enterprise (NCC-1701)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursOnStarship Context triple: [Nomad begins altering Enterprise systems, occursOnStarship, USS Enterprise (NCC-1701)]
-
A.
usedOnStarships
Indicates that something is employed or applied in the context of starships, such as equipment, technology, or materials used aboard or for operating them.
-
B.
hasStarshipClassDepicted
Indicates that an entity includes or shows a depiction of a particular starship class.
-
C.
hasStarship
Indicates that one entity possesses, controls, or is associated with a particular starship.
-
D.
starshipServedOn
Indicates that a person was assigned to and served aboard a particular starship.
-
E.
usesStarshipClass
Indicates that an entity operates, employs, or is associated with a particular class or type of starship.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: May 3, 2026, 4:02 p.m.