Triple
T38591951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silithid |
E932473
|
entity |
| Predicate | hasMountVariant |
P455
|
FINISHED |
| Object | Silithid Tank mount |
—
|
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: Silithid Tank mount | Statement: [Silithid, hasMountVariant, Silithid Tank mount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMountVariant Context triple: [Silithid, hasMountVariant, Silithid Tank mount]
-
A.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
B.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
C.
hasSummitVariant
Indicates that an entity has a specific summit-related version or variant associated with it.
-
D.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
E.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: May 3, 2026, 4:32 p.m.