Triple
T8899063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Oxhey |
E211878
|
entity |
| Predicate | builtToHouse |
P43310
|
FINISHED |
| Object | London overspill population |
—
|
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: London overspill population | Statement: [South Oxhey, builtToHouse, London overspill population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtToHouse Context triple: [South Oxhey, builtToHouse, London overspill population]
-
A.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
-
B.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
-
C.
houseProduced
chosen
Indicates that a house or housing unit was created, built, or generated by a particular agent, process, or source.
-
D.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
-
E.
buildingConvertedTo
Indicates that one building has been transformed, repurposed, or adapted into another type or use of building.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc642618908190b3df50cbbabff93d |
completed | April 1, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2bfb38819083d5eb1af8ccf4d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:54 p.m.