Triple
T9585648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Temple |
E231281
|
entity |
| Predicate | translatedToSeeOfLondon |
P89946
|
FINISHED |
| Object | 1885 |
—
|
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: 1885 | Statement: [Frederick Temple, translatedToSeeOfLondon, 1885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translatedToSeeOfLondon Context triple: [Frederick Temple, translatedToSeeOfLondon, 1885]
-
A.
metropolitanSee
Indicates a relationship where one metropolitan area views, oversees, or conceptually regards another place, entity, or aspect within its sphere of influence.
-
B.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
C.
transferredToLondonUnderground
Indicates that something or someone has been moved from a previous context or system into the London Underground network or organization.
-
D.
locationOfSee
Indicates a relationship where a particular place is the setting or site in which an act of seeing or visual perception occurs.
-
E.
returnedToEngland
Indicates that an entity went back to England after having been away.
- F. None of above. chosen
Provenance (4 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99edc2c08190b67b40f6214d46f1 |
completed | April 1, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:06 p.m.