Triple

T37513558
Position Surface form Disambiguated ID Type / Status
Subject Act III E932573 entity
Predicate hasTownPortalDestination P194886 FINISHED
Object Kurast Docks 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: Kurast Docks | Statement: [Act III, hasTownPortalDestination, Kurast Docks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTownPortalDestination
Context triple: [Act III, hasTownPortalDestination, Kurast Docks]
  • A. hasNearbyTown
    Indicates that one location has a town situated close to it in geographic proximity.
  • B. hasPilgrimageDestinationAtEnd
    Indicates that an entity’s journey or process culminates at a specific location regarded as its pilgrimage destination.
  • C. containsPilgrimageTown
    Indicates that a place or region includes within its boundaries a town that serves as a destination or center for religious pilgrimage.
  • D. hasTramDestination
    Indicates that a tram route or service goes to or terminates at a specified destination.
  • E. hasAccessToTown
    Indicates that one entity is permitted or able to enter, use, or otherwise access a particular town.
  • 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_69f76ec730988190b5aa4f9cb9afd518 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd8ccbd4c88190b13aae0673b3c821 completed May 8, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69fd8ae2227c819089546f5c3629799e completed May 8, 2026, 7:04 a.m.
PDg Predicate description generation batch_69fd8ccaee848190acd59d7d643ad062 completed May 8, 2026, 7:12 a.m.
Created at: May 3, 2026, 4:17 p.m.