Triple

T37513591
Position Surface form Disambiguated ID Type / Status
Subject Spider Forest E932574 entity
Predicate containsWaypoint P99973 FINISHED
Object Spider Forest waypoint 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: Spider Forest waypoint | Statement: [Spider Forest, containsWaypoint, Spider Forest waypoint]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsWaypoint
Context triple: [Spider Forest, containsWaypoint, Spider Forest waypoint]
  • A. hasWaypoint chosen
    Indicates that an entity follows a path or route that includes a specific intermediate location (waypoint) along its trajectory.
  • B. containsPoint
    Indicates that a geometric region or shape includes a given point within its boundaries.
  • C. isTransitPointOn
    Indicates that one location serves as an intermediate transit point along a specified route, path, or journey.
  • D. hasAlongRoute
    Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
  • E. isWanderingPoint
    Indicates that an entity is moving aimlessly or without a fixed destination within a given space or context.
  • 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_69f76ec730988190b5aa4f9cb9afd518 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a01b130f6808190b86442fb16930e6e completed May 11, 2026, 10:36 a.m.
PD Predicate disambiguation batch_6a01b023157881909a802e06eced3e2f completed May 11, 2026, 10:32 a.m.
Created at: May 3, 2026, 4:17 p.m.