Triple
T2678270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deportivo de La Coruña |
E56511
|
entity |
| Predicate | participationPeriod |
P4470
|
FINISHED |
| Object | European competitions in late 1990s |
—
|
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: European competitions in late 1990s | Statement: [Deportivo de La Coruña, participationPeriod, European competitions in late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participationPeriod Context triple: [Deportivo de La Coruña, participationPeriod, European competitions in late 1990s]
-
A.
preparationPeriod
Indicates the time span allocated before an event or action during which necessary preparations are made.
-
B.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
-
C.
participation
chosen
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
D.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
E.
hasAwardPeriod
Indicates the time span or date range during which an award is valid, active, or applicable.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abda2f7bf88190a1e3103dd014d871 |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ab9d08190b72b6104c6dbc769 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.