Triple
T36957671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billy Blaze |
E914229
|
entity |
| Predicate | spaceshipName |
P186535
|
FINISHED |
| Object | Bean-with-Bacon Megarocket |
—
|
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: Bean-with-Bacon Megarocket | Statement: [Billy Blaze, spaceshipName, Bean-with-Bacon Megarocket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceshipName Context triple: [Billy Blaze, spaceshipName, Bean-with-Bacon Megarocket]
-
A.
starshipRegistry
Indicates a formal registration relationship where a starship is recorded in an official registry or database.
-
B.
hostSpacecraftAlternateName
chosen
Indicates that an alternative or secondary name is used to refer to the host spacecraft.
-
C.
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.
-
D.
hasStarship
Indicates that one entity possesses, controls, or is associated with a particular starship.
-
E.
starshipServedOn
Indicates that a person was assigned to and served aboard 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:13 p.m.