Triple
T38110625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galakrond, the Wretched |
E951643
|
entity |
| Predicate | hasExpansionKeyword |
P194506
|
FINISHED |
| Object | Invoke |
—
|
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: Invoke | Statement: [Galakrond, the Wretched, hasExpansionKeyword, Invoke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpansionKeyword Context triple: [Galakrond, the Wretched, hasExpansionKeyword, Invoke]
-
A.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
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.
hasExpansionModel
Indicates that one entity is associated with a specific model or schema used to define how it can be expanded, detailed, or elaborated.
-
E.
hasExpansionPattern
Indicates that an entity follows or is associated with a specific pattern or manner of expansion.
- F. None of above. chosen
Provenance (4 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: May 3, 2026, 4:21 p.m.