Triple

T38685391
Position Surface form Disambiguated ID Type / Status
Subject Integrated Truss Structure S0 segment E949101 entity
Predicate connectedSegmentDirection P82340 FINISHED
Object port side truss elements 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: port side truss elements | Statement: [Integrated Truss Structure S0 segment, connectedSegmentDirection, port side truss elements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectedSegmentDirection
Context triple: [Integrated Truss Structure S0 segment, connectedSegmentDirection, port side truss elements]
  • A. segmentDirected
    Indicates that one segment has a specified direction or orientation from one endpoint toward another.
  • B. branchLineDirection
    Indicates the directional orientation or flow of a branch line relative to a main line or reference point.
  • C. connectionDirection chosen
    Indicates the directional flow or orientation of a connection from one entity to another.
  • D. containsDirectionOf
    Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
  • E. isAlternateSegmentOf
    Indicates that one segment serves as an alternative or substitute to another segment, typically in a sequence, structure, or path.
  • 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_69f76efe16148190befd5dd59c3dfeaa completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a002ae74da08190a4b47e0ff0f7f8fe completed May 10, 2026, 6:51 a.m.
PD Predicate disambiguation batch_6a0029cc369c81909578e52c4a75ab18 completed May 10, 2026, 6:46 a.m.
Created at: May 3, 2026, 4:33 p.m.