Triple
T27872308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MG-100 StarFortress SF-17 |
E704821
|
entity |
| Predicate | fictional spacecraft |
P69373
|
FINISHED |
| Object | Star Wars universe |
—
|
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: Star Wars universe | Statement: [MG-100 StarFortress SF-17, fictional spacecraft, Star Wars universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictional spacecraft Context triple: [MG-100 StarFortress SF-17, fictional spacecraft, Star Wars universe]
-
A.
fictionalShip
chosen
Indicates that one entity is a ship that exists only in fiction or narrative works, rather than in reality.
-
B.
hasStarshipClassDepicted
Indicates that an entity includes or shows a depiction of a particular starship class.
-
C.
starshipRegistry
Indicates a formal registration relationship where a starship is recorded in an official registry or database.
-
D.
hasStarship
Indicates that one entity possesses, controls, or is associated with a particular starship.
-
E.
fictionalObject
Indicates that one entity is a fictional or imaginary object in relation to another entity.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 6:25 p.m.