Triple
T15659456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frente Central de la Guerra Civil Española |
E376530
|
entity |
| Predicate | inicioAproximado |
P48368
|
FINISHED |
| Object | noviembre de 1936 |
—
|
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: noviembre de 1936 | Statement: [Frente Central de la Guerra Civil Española, inicioAproximado, noviembre de 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inicioAproximado Context triple: [Frente Central de la Guerra Civil Española, inicioAproximado, noviembre de 1936]
-
A.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
C.
startOfConstructionApprox
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
-
D.
initialOpening
Indicates the first or earliest instance in which something is opened, begun, or made accessible.
-
E.
approximateIntroductionPeriod
Indicates the approximate time period during which an entity was first introduced or came into use.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef4e6a08190ad8bbafaa3612f22 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.