Triple
T38368584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-1 starfighter |
E892517
|
entity |
| Predicate | customVariantOf |
P152595
|
FINISHED |
| Object | Din Djarin’s N-1 starfighter |
—
|
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: Din Djarin’s N-1 starfighter | Statement: [N-1 starfighter, customVariantOf, Din Djarin’s N-1 starfighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customVariantOf Context triple: [N-1 starfighter, customVariantOf, Din Djarin’s N-1 starfighter]
-
A.
customizedVariantOf
chosen
Indicates that one entity is a modified or tailored version derived from another, preserving a core basis while introducing specific customizations.
-
B.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
C.
designVariant
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
-
D.
exportVariantName
Indicates that one entity is the name or label of a specific variant of another entity intended for export.
-
E.
parameterizedVariant
Indicates that one entity is a specific parameterized form or configuration variant derived from another base 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.