Triple
T37554452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydraxian Waterlords |
E933660
|
entity |
| Predicate | expansionRelevance |
P193164
|
FINISHED |
| Object | primarily Classic |
—
|
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: primarily Classic | Statement: [Hydraxian Waterlords, expansionRelevance, primarily Classic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionRelevance Context triple: [Hydraxian Waterlords, expansionRelevance, primarily Classic]
-
A.
expansionLinkedTo
Indicates that one entity’s growth, increase, or enlargement is causally or logically connected to the expansion of another entity.
-
B.
limitsExpansionOf
Indicates that one entity restricts or constrains the growth, spread, or further development of another entity.
-
C.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
D.
restrictedExpansionOf
Indicates a relationship where one entity is an expansion of another, but with added constraints or limitations that make it more specific or narrowly applicable than the original.
-
E.
expansionReason
Indicates the reason or cause behind an expansion event or process occurring between entities.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 3, 2026, 4:17 p.m.