Triple
T15149896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigrid plain |
E361908
|
entity |
| Predicate | etymologyPossiblyMeans |
P15774
|
FINISHED |
| Object | battle-surge |
—
|
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: battle-surge | Statement: [Vigrid plain, etymologyPossiblyMeans, battle-surge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyPossiblyMeans Context triple: [Vigrid plain, etymologyPossiblyMeans, battle-surge]
-
A.
etymologyPossibleMeaning
chosen
Indicates a possible or hypothesized meaning that an etymological analysis suggests for a word or term.
-
B.
etymologicalRootMeaning
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
C.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
D.
etymologyGloss
Indicates that a term’s meaning is explained by a brief gloss specifically describing its etymological origin or source.
-
E.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c934048190afac78a8023a544a |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.