Triple
T38065401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Pancras, Soper Lane |
E950456
|
entity |
| Predicate | laterUnitedWith |
P7838
|
FINISHED |
| Object | St Mary-le-Bow |
—
|
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: St Mary-le-Bow | Statement: [St Pancras, Soper Lane, laterUnitedWith, St Mary-le-Bow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterUnitedWith Context triple: [St Pancras, Soper Lane, laterUnitedWith, St Mary-le-Bow]
-
A.
wasUnifiedWith
chosen
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
B.
oftenUnitedWith
Indicates that two entities are frequently joined, combined, or associated together as a common or recurring unit.
-
C.
unites
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
D.
laterAnnexedTo
Indicates that one entity was annexed by another entity at a later point in time, after its initial status or affiliation.
-
E.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:21 p.m.