Triple

T26818779
Position Surface form Disambiguated ID Type / Status
Subject MIEMSS E675189 entity
Predicate systemCoordinated P82071 FINISHED
Object Maryland emergency medical services system NE NERFINISHED

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: Maryland emergency medical services system | Statement: [MIEMSS, systemCoordinated, Maryland emergency medical services system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: systemCoordinated
Context triple: [MIEMSS, systemCoordinated, Maryland emergency medical services system]
  • A. coordinateSystem
    Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
  • B. coordinateSystemObserved
    Indicates that one entity is observed, measured, or expressed within the reference frame or coordinate system defined by another entity.
  • C. currentSystem
    Indicates that an entity is the system or configuration that is presently active or in use.
  • D. coordinateSystemBehavior
    Indicates how positions, orientations, or transformations are defined, interpreted, and updated within a particular coordinate system.
  • E. coordinateOn chosen
    Indicates that two or more entities work together to organize, align, or manage a shared activity, process, or objective.
  • 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_69eee9b6b28481909332f83eb17e5170 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f6691f5e188190b12c7b2eb729a45e completed May 2, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69f66598d6008190a7ca8ff80399fd34 completed May 2, 2026, 8:59 p.m.
Created at: April 27, 2026, 4:53 a.m.