Triple
T38584431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellfire Ramparts |
E932313
|
entity |
| Predicate | travelHubNearby |
P191056
|
FINISHED |
| Object | Hellfire Peninsula Dark Portal |
—
|
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: Hellfire Peninsula Dark Portal | Statement: [Hellfire Ramparts, travelHubNearby, Hellfire Peninsula Dark Portal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelHubNearby Context triple: [Hellfire Ramparts, travelHubNearby, Hellfire Peninsula Dark Portal]
-
A.
nearestTouristDestination
Indicates that one location is the closest tourist destination to another specified location.
-
B.
travelHub
chosen
Indicates a location that serves as a central node or major interchange point for travel or transportation connections between different places or routes.
-
C.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
-
D.
nearbyHeritageDestinations
Indicates that one or more heritage destinations are located close to a given reference point or entity in geographic space.
-
E.
nearbyVenue
Indicates that one venue is located close to another venue in physical space.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:32 p.m.