Triple
T9115489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of Ecuador in London |
E218709
|
entity |
| Predicate | startOfAsylum |
P32939
|
FINISHED |
| Object | 2012-06-19 |
—
|
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: 2012-06-19 | Statement: [Embassy of Ecuador in London, startOfAsylum, 2012-06-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfAsylum Context triple: [Embassy of Ecuador in London, startOfAsylum, 2012-06-19]
-
A.
startOfEmbassyAsylum
chosen
Indicates the point in time when an individual's period of asylum within an embassy officially begins.
-
B.
attemptedToSeekAsylumIn
Indicates that an entity tried, but may not have succeeded, to obtain asylum in a particular place or country.
-
C.
soughtAsylumBy
Indicates that one party has requested protection or refuge (asylum) from another authority or country.
-
D.
soughtAsylumAt
Indicates that an individual or group applied for protection or refuge at a particular country, institution, or authority.
-
E.
receivedAsylumFrom
Indicates that one entity was granted asylum or refuge by another entity, typically a state or institution.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a1340881909dc791b825e87ef2 |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.