Triple
T15857859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CESCE |
E384505
|
entity |
| Predicate | hasPlayedKeyRoleIn |
P3512
|
FINISHED |
| Object | ownership of Indra Sistemas |
—
|
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: ownership of Indra Sistemas | Statement: [CESCE, hasPlayedKeyRoleIn, ownership of Indra Sistemas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayedKeyRoleIn Context triple: [CESCE, hasPlayedKeyRoleIn, ownership of Indra Sistemas]
-
A.
playedKeyRoleIn
chosen
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
-
B.
hasPlayedRole
Indicates that an entity has performed or portrayed a particular role or character in some context (such as a film, play, or production).
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
alsoPlayed
Indicates that the same entity participated in or performed in an additional role, work, or context beyond the one already specified.
-
E.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:50 a.m.