Triple
T11626230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estadio Nacional Julio Martínez Prádanos |
E276275
|
entity |
| Predicate | usedAsDetentionCenterUntil |
P15559
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Estadio Nacional Julio Martínez Prádanos, usedAsDetentionCenterUntil, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsDetentionCenterUntil Context triple: [Estadio Nacional Julio Martínez Prádanos, usedAsDetentionCenterUntil, 1974]
-
A.
placeOfDetention
Indicates the location or facility where an entity is or was held in detention.
-
B.
usedToDetain
Indicates that something serves or functioned as a means, tool, or facility for holding or confining someone against their will.
-
C.
usedForImprisoning
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
-
D.
periodOfUseAsPrison
chosen
Indicates the time span during which something functioned or was used as a prison.
-
E.
wasDetainedDuring
Indicates that an entity was held in custody or confinement for some period of time during a specified event or time interval.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a12416908190ac2dcd7f7ebb308f |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.