Triple

T12883127
Position Surface form Disambiguated ID Type / Status
Subject Porto Metro E308152 entity
Predicate hasElevatedSections P107430 FINISHED
Object yes 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: yes | Statement: [Porto Metro, hasElevatedSections, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasElevatedSections
Context triple: [Porto Metro, hasElevatedSections, yes]
  • A. hasElevatedBranch
    Indicates that one entity possesses or features a branch that is positioned higher or raised relative to a reference level or structure.
  • B. hasVerticalSection
    Indicates that one entity possesses or includes a distinct vertical section or segment as part of its structure or representation.
  • C. hasLowLevelSection
    Indicates that an entity includes or is associated with a subordinate or lower-level section within a larger hierarchical structure.
  • D. notableElevatedSection
    Indicates that a particular segment or portion of something is raised or elevated relative to its surroundings in a way that is especially significant or noteworthy.
  • E. hasSect
    Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
  • 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_69d7bdf69bc48190af6c2621f28ca351 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d97c7f91d08190aac2f6419d3ba992 completed April 10, 2026, 10:41 p.m.
PD Predicate disambiguation batch_69d96fa55b888190ab1612e93c41aec4 completed April 10, 2026, 9:46 p.m.
PDg Predicate description generation batch_69d97c7d0598819080cab0a2314bc106 completed April 10, 2026, 10:41 p.m.
Created at: April 9, 2026, 5:39 p.m.