Triple

T9676466
Position Surface form Disambiguated ID Type / Status
Subject Reparto Mobile E234164 entity
Predicate typicalDeploymentContext P37480 FINISHED
Object demonstrations — 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: demonstrations | Statement: [Reparto Mobile, typicalDeploymentContext, demonstrations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalDeploymentContext
Context triple: [Reparto Mobile, typicalDeploymentContext, demonstrations]
  • A. typicalDeployment
    Indicates that one entity represents the standard or most commonly used deployment configuration or pattern for the other entity.
  • B. typeOfDeployment
    Indicates the specific manner or configuration in which something (such as a system, application, or resource) is deployed or made operational.
  • C. deploymentType
    Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
  • D. firstDeploymentContext
    Indicates the context, environment, or situation in which something (typically a system, product, or capability) is initially deployed or put into operational use.
  • E. hasTypicalUseContext chosen
    Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
  • 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_69ca848f55e48190b3f67252571c3d45 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9c99ee0481908ead5f7112117c90 completed April 1, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69ccd5b5d40c8190850ad7a351445f32 completed April 1, 2026, 8:22 a.m.
Created at: March 30, 2026, 8:15 p.m.