Triple

T36598123
Position Surface form Disambiguated ID Type / Status
Subject ESRI Shapefile E902852 entity
Predicate coordinateSystemStorage P186061 FINISHED
Object .prj file 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: .prj file | Statement: [ESRI Shapefile, coordinateSystemStorage, .prj file]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coordinateSystemStorage
Context triple: [ESRI Shapefile, coordinateSystemStorage, .prj file]
  • A. coordinateSystem
    Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
  • B. coordinateSystemBehavior
    Indicates how positions, orientations, or transformations are defined, interpreted, and updated within a particular coordinate system.
  • C. coordinateSystemObserved
    Indicates that one entity is observed, measured, or expressed within the reference frame or coordinate system defined by another entity.
  • D. coordinates
    Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
  • E. coordinatesMode
    Indicates that one entity specifies or controls the coordinate system or reference frame used to interpret the spatial data of another entity.
  • 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_69f76e66b7b88190848f7a3e1188915f completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c83f5960819089610ed39c839678 completed May 3, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69f7c477a4d481908f52e55b6688f60c completed May 3, 2026, 9:56 p.m.
PDg Predicate description generation batch_69f7c776b4088190bef550c869da530d completed May 3, 2026, 10:08 p.m.
Created at: May 3, 2026, 4:11 p.m.