Triple
T13765592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dapitan City |
E330731
|
entity |
| Predicate | hasExilePeriodOfJoséRizal |
P34025
|
FINISHED |
| Object | 1892–1896 |
—
|
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: 1892–1896 | Statement: [Dapitan City, hasExilePeriodOfJoséRizal, 1892–1896]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExilePeriodOfJoséRizal Context triple: [Dapitan City, hasExilePeriodOfJoséRizal, 1892–1896]
-
A.
periodOfExile
chosen
Indicates a time span during which an entity is banished, expelled, or forced to live away from its native or rightful place.
-
B.
hasPreviousExile
Indicates that an entity has experienced at least one prior period of exile before the current or referenced state.
-
C.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
-
D.
exileStart
Indicates the point in time or event when an entity begins being forced to live away from its home or native place.
-
E.
livedInExileIn
Indicates that an entity spent a period of time living outside its home country or usual place of residence due to exile, in a specified location.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de022690ac8190bd5410ecc659a2a7 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.