Triple
T25187368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaylon–Union war |
E630753
|
entity |
| Predicate | involvesStarship |
P108461
|
FINISHED |
| Object | USS Orville (ECV-197) |
—
|
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 Orville (ECV-197) | Statement: [Kaylon–Union war, involvesStarship, USS Orville (ECV-197)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesStarship Context triple: [Kaylon–Union war, involvesStarship, USS Orville (ECV-197)]
-
A.
starshipCommanded
Indicates that one entity serves as the commanding officer or authority in charge of operating and directing the other entity, which is a starship.
-
B.
starshipServedOn
Indicates that a person was assigned to and served aboard a particular starship.
-
C.
followsStarship
Indicates that one entity moves or travels behind a specific starship, maintaining pursuit or trailing its course.
-
D.
starshipRegistry
Indicates a formal registration relationship where a starship is recorded in an official registry or database.
-
E.
hasStarship
chosen
Indicates that one entity possesses, controls, or is associated with a particular starship.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 12:44 p.m.