Triple
T32061087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gale Cumulus |
E818749
|
entity |
| Predicate | hasElementalNeighbors |
P180660
|
FINISHED |
| Object | fire residents of Element City |
—
|
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: fire residents of Element City | Statement: [Gale Cumulus, hasElementalNeighbors, fire residents of Element City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElementalNeighbors Context triple: [Gale Cumulus, hasElementalNeighbors, fire residents of Element City]
-
A.
hasNeighboringSite
Indicates that one site is located adjacent to or directly next to another site.
-
B.
hasNeighbouringUnit
Indicates that one unit is directly adjacent to and shares a boundary or side with another unit.
-
C.
isVolcanicNeighborOf
Indicates that one geographic feature is located close enough to another volcanic feature that they are considered neighboring volcano-related entities.
-
D.
hasNeighborAcrossFjord
Indicates that one entity is located across a fjord from another entity, such that they are neighbors separated by the fjord.
-
E.
hasSurroundings
Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: May 1, 2026, 12:21 a.m.