Triple

T12814332
Position Surface form Disambiguated ID Type / Status
Subject Imperial Express SuperChair E306351 entity
Predicate terrainAccess P103580 FINISHED
Object advanced terrain 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: advanced terrain | Statement: [Imperial Express SuperChair, terrainAccess, advanced terrain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: terrainAccess
Context triple: [Imperial Express SuperChair, terrainAccess, advanced terrain]
  • A. trailAccess
    Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
  • B. terrainIncludes
    Indicates that a specified terrain area contains or encompasses another geographic or environmental feature within its boundaries.
  • C. terrainFeature
    Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
  • D. involvesTerrain chosen
    Indicates that the relationship or action takes place in, across, or is directly affected by a specified type of terrain or landform.
  • E. hasScenicAccessTo
    Indicates that one place or object provides a visually appealing or notable view of another place or object.
  • 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_69d7bdf46c448190b1faa55aaacb6317 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e9beb30819097c256a5aab9a4c8 completed April 10, 2026, 9:41 p.m.
PD Predicate disambiguation batch_69d9640ed7448190b276e7fab649f7d2 completed April 10, 2026, 8:56 p.m.
Created at: April 9, 2026, 5:31 p.m.