Triple
T25418254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagenham |
E636904
|
entity |
| Predicate | absorbedVillage |
P158281
|
FINISHED |
| Object | Village of Dagenham |
—
|
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: Village of Dagenham | Statement: [Dagenham, absorbedVillage, Village of Dagenham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: absorbedVillage Context triple: [Dagenham, absorbedVillage, Village of Dagenham]
-
A.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
-
C.
capitalVillage
Indicates that a village serves as the administrative or political capital of a specified region or entity.
-
D.
servesVillage
Indicates that an entity provides services, support, or functions that benefit or are directed toward a particular village.
-
E.
worstAffectedVillage
Indicates that the village is the one most severely impacted or damaged in a given event or situation.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b013596c81909af7acebfc72bfc6 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:55 p.m.