Triple

T5316459
Position Surface form Disambiguated ID Type / Status
Subject Rote Insel E119161 entity
Predicate transportBarrier P53911 FINISHED
Object railway embankments 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: railway embankments | Statement: [Rote Insel, transportBarrier, railway embankments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transportBarrier
Context triple: [Rote Insel, transportBarrier, railway embankments]
  • A. transportInterface
    Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
  • B. typicalBarrierType chosen
    Indicates the usual or characteristic type of barrier associated with or used in a given context or situation.
  • C. transportAgnostic
    Indicates that the relationship or action is independent of, and unaffected by, the specific transport mechanism or communication channel used.
  • D. transportGoal
    Indicates that an entity has the objective or intended outcome of moving or conveying something or someone from one place to another.
  • E. createsBarrierFor
    Indicates that one entity causes an obstruction, hindrance, or impediment that makes it more difficult for another entity to act, move, or achieve something.
  • 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_69bd446b57bc8190a513d2e6c40314f3 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd86f20f008190be7b5848af05f2b8 completed March 20, 2026, 5:42 p.m.
PD Predicate disambiguation batch_69bd84534f9c8190bc19d4812060768d completed March 20, 2026, 5:30 p.m.
Created at: March 20, 2026, 1:54 p.m.