Triple
T37401906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purfleet-on-Thames |
E929014
|
entity |
| Predicate | adoptedNameFrom |
P91408
|
FINISHED |
| Object | Purfleet |
—
|
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: Purfleet | Statement: [Purfleet-on-Thames, adoptedNameFrom, Purfleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedNameFrom Context triple: [Purfleet-on-Thames, adoptedNameFrom, Purfleet]
-
A.
adoptedFamilyName
Indicates that an entity has taken or been given a family name different from their original one, typically through adoption, marriage, or personal choice.
-
B.
currentNameAdoptedBy
Indicates that an entity has adopted or started using a particular current name.
-
C.
adoptedNewNameDueTo
Indicates that an entity changed its original name to a new one as a result of, or in response to, another specified entity or circumstance.
-
D.
adoptedFrom
chosen
Indicates that an entity has been taken into guardianship, ownership, or use from another source or origin.
-
E.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.