Triple
T113465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Expulsion of 1492 |
E2293
|
entity |
| Predicate | yearCoincidesWith |
P4822
|
FINISHED |
| Object | 1492 discovery of the Americas |
—
|
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: 1492 discovery of the Americas | Statement: [Spanish Expulsion of 1492, yearCoincidesWith, 1492 discovery of the Americas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearCoincidesWith Context triple: [Spanish Expulsion of 1492, yearCoincidesWith, 1492 discovery of the Americas]
-
A.
observesSameTimeAs
chosen
Indicates that two observation events occur simultaneously or during the same time interval.
-
B.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
C.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
D.
meetsDuring
Indicates that one entity encounters or comes together with another while a specified event or time interval is in progress.
-
E.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564417848190a8a8a38e97348963 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.