Triple

T28478802
Position Surface form Disambiguated ID Type / Status
Subject Centros de simulación del Ejército de Tierra de España E720634 entity
Predicate utiliza P73516 FINISHED
Object sistemas de simulación avanzados 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: sistemas de simulación avanzados | Statement: [Centros de simulación del Ejército de Tierra de España, utiliza, sistemas de simulación avanzados]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: utiliza
Context triple: [Centros de simulación del Ejército de Tierra de España, utiliza, sistemas de simulación avanzados]
  • A. uso chosen
    Indicates that one entity uses, employs, or makes use of another entity for some purpose or function.
  • B. usedVia
    Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
  • C. utility
    Indicates that something provides usefulness, benefit, or practical value to an entity or in a given context.
  • D. denUse
    Indicates that an entity uses or makes use of a particular den (or designated shelter/space) for its activities or habitation.
  • E. usedWith
    Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
  • 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_69f01a5983f48190b7c1b8857245a4f7 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64ee7eb088190a195cefc30aa4fff completed May 2, 2026, 7:22 p.m.
PD Predicate disambiguation batch_69f64caede108190a35cc7cbfead866f completed May 2, 2026, 7:12 p.m.
Created at: April 28, 2026, 2:54 a.m.