Triple
T37507485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waystone from Oribos |
E932134
|
entity |
| Predicate | destinationZone |
P83648
|
FINISHED |
| Object | the Maw |
—
|
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: the Maw | Statement: [Waystone from Oribos, destinationZone, the Maw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationZone Context triple: [Waystone from Oribos, destinationZone, the Maw]
-
A.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
B.
territoryOfDestination
Indicates that a specified territory is the destination or endpoint location associated with an action, movement, or relation.
-
C.
timeZoneDestination
Indicates the time zone associated with the destination location in a given context or event.
-
D.
destinationFeature
Indicates the feature, place, or element that serves as the endpoint or target location of a movement, transfer, or directed relation.
-
E.
hasDestinationRegion
chosen
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.