Triple
T27914998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MC85 Star Cruiser Raddus |
E706044
|
entity |
| Predicate | fictionalEntity |
P84710
|
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: [MC85 Star Cruiser Raddus, fictionalEntity, Star Wars universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalEntity Context triple: [MC85 Star Cruiser Raddus, fictionalEntity, Star Wars universe]
-
A.
fictionalEntityType
Indicates that the subject is classified as a particular type or category of fictional entity within a narrative or imaginary context.
-
B.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
C.
fictionalObject
chosen
Indicates that one entity is a fictional or imaginary object in relation to another entity.
-
D.
fictionalCharacterFrom
Indicates that a fictional character originates from, or is created within, a particular work, universe, or source.
-
E.
fictionalCharacterAssisted
Indicates that one fictional character provided help, support, or assistance to another fictional character.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 6:53 p.m.