Triple
T37463068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Mosh |
E930965
|
entity |
| Predicate | hasExpansionKeywordContext |
P191849
|
FINISHED |
| Object | Un'Goro dinosaurs |
—
|
LITERAL FINISHED |
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: Un'Goro dinosaurs | Statement: [King Mosh, hasExpansionKeywordContext, Un'Goro dinosaurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpansionKeywordContext Context triple: [King Mosh, hasExpansionKeywordContext, Un'Goro dinosaurs]
-
A.
expansionKeywordContext
chosen
Indicates the contextual relationship in which a keyword is expanded or interpreted, linking the keyword to the surrounding content or query intent.
-
B.
hasExpansionType
Indicates that an entity is associated with a particular mode or category of expansion (such as how it grows, extends, or scales).
-
C.
hasExpansionName
Indicates that an entity has a specific name used for its expanded or extended form.
-
D.
hasExpansionPattern
Indicates that an entity follows or is associated with a specific pattern or manner of expansion.
-
E.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:17 p.m.