Triple
T13906583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harlow, Essex, England |
E334367
|
entity |
| Predicate | developmentCorporationEstablishedYear |
P111960
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Harlow, Essex, England, developmentCorporationEstablishedYear, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentCorporationEstablishedYear Context triple: [Harlow, Essex, England, developmentCorporationEstablishedYear, 1947]
-
A.
foundedCompany
Indicates that an entity established or created a company, typically as its founder or co-founder.
-
B.
companyIncorporatedIn
Indicates that a company was legally formed and registered in a specified jurisdiction or location.
-
C.
associatedCompanySpinOffYear
Indicates the year in which a related or associated company was spun off from its original parent organization.
-
D.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
-
E.
associatedCompanyFoundedIn
Indicates that the related company was founded in the specified year or time period.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25dc26cc8190a7909980b1d34933 |
completed | April 14, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:16 p.m.