Triple
T37551727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borean Tundra |
E933604
|
entity |
| Predicate | oppositeStarterZone |
P194928
|
FINISHED |
| Object | Howling Fjord |
—
|
NE NERFINISHED |
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: Howling Fjord | Statement: [Borean Tundra, oppositeStarterZone, Howling Fjord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeStarterZone Context triple: [Borean Tundra, oppositeStarterZone, Howling Fjord]
-
A.
opposedDirectionRegion
Indicates that one region is oriented in the exact opposite direction relative to another region.
-
B.
opposingLocation
Indicates that two entities are located directly opposite each other, typically across a defined reference such as a street, corridor, or boundary.
-
C.
startingZoneFor
Indicates the zone or area where an entity initially begins, is placed, or starts its activity or process.
-
D.
opposingStarPlayer
Indicates that one player is the primary or notable player on the opposing team relative to another player or team.
-
E.
opponentPosition
Indicates the spatial location or placement of an opposing entity relative to a reference entity or context.
- 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_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
| PDg | Predicate description generation | batch_69fd8e5e9ca48190890a2caddc1f9f5c |
completed | May 8, 2026, 7:18 a.m. |
Created at: May 3, 2026, 4:17 p.m.