Triple
T36841176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Survey of London |
E910410
|
entity |
| Predicate | hasLaterEditor |
P41706
|
FINISHED |
| Object | Charles Lethbridge Kingsford |
—
|
NE NERFINISHED |
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: Charles Lethbridge Kingsford | Statement: [A Survey of London, hasLaterEditor, Charles Lethbridge Kingsford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterEditor Context triple: [A Survey of London, hasLaterEditor, Charles Lethbridge Kingsford]
-
A.
hasFormerEditor
Indicates that an entity previously served as the editor of another entity but no longer holds that editorial role.
-
B.
laterEditor
chosen
Indicates that one entity served as an editor of a work at a later time or in a subsequent edition relative to another editor.
-
C.
hasModernEditor
Indicates that an entity is associated with, or has been prepared or revised by, a contemporary editor.
-
D.
hasEditorType
Indicates that an entity has an associated kind or category of editor responsible for reviewing or modifying it.
-
E.
intendedEditor
Indicates that one entity is designated or expected to act as the editor of another entity (such as a document, work, or content).
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:13 p.m.