Triple
T28478889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oficiales del Ejército de Tierra de España |
E720636
|
entity |
| Predicate | tienenFunción |
P68285
|
FINISHED |
| Object | conducción de unidades terrestres |
—
|
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: conducción de unidades terrestres | Statement: [oficiales del Ejército de Tierra de España, tienenFunción, conducción de unidades terrestres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tienenFunción Context triple: [oficiales del Ejército de Tierra de España, tienenFunción, conducción de unidades terrestres]
-
A.
기능
chosen
Indicates that an entity has a particular function, role, or operational capability.
-
B.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
C.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
D.
definesFunctioningOf
Indicates that one entity specifies or determines how another entity operates or functions.
-
E.
providesFunctionalityOf
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 2:54 a.m.