Triple
T28478903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oficiales del Ejército de Tierra de España |
E720636
|
entity |
| Predicate | incluyenRango |
P86530
|
FINISHED |
| Object | alférez |
—
|
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: alférez | Statement: [oficiales del Ejército de Tierra de España, incluyenRango, alférez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incluyenRango Context triple: [oficiales del Ejército de Tierra de España, incluyenRango, alférez]
-
A.
tieneRango
Indicates that one entity possesses, is assigned, or falls within a specific rank or range in relation to another entity.
-
B.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
C.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
D.
includesRange
chosen
Indicates that one entity’s span, interval, or range fully contains or covers the span, interval, or range of another entity.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: April 28, 2026, 2:54 a.m.