Triple
T14699456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilford, Essex, England |
E345253
|
entity |
| Predicate | incorporatedIntoDate |
P58754
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [Ilford, Essex, England, incorporatedIntoDate, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatedIntoDate Context triple: [Ilford, Essex, England, incorporatedIntoDate, 1965]
-
A.
incorporatedIntoOnDate
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
B.
laterIncorporatedInto
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
C.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
D.
incorporationCompletedBy
Indicates that the completion of an incorporation process is carried out or effected by a specific agent or entity.
-
E.
integratedDate
chosen
Indicates the date on which one entity was incorporated, combined, or brought into a larger system or whole.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb604f88081908a677175045496d0 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.