Triple
T7979747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lymm Village Conservation Area |
E185538
|
entity |
| Predicate | hasBuiltForm |
P44411
|
FINISHED |
| Object | mixed historic building styles |
—
|
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: mixed historic building styles | Statement: [Lymm Village Conservation Area, hasBuiltForm, mixed historic building styles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuiltForm Context triple: [Lymm Village Conservation Area, hasBuiltForm, mixed historic building styles]
-
A.
hasBuilt
Indicates that one entity is the creator or constructor of another entity.
-
B.
hasBuildingForm
chosen
Indicates that an entity possesses or is characterized by a particular architectural or structural building form.
-
C.
hasFormed
Indicates that an entity has come together or been created into a particular structure, group, or configuration.
-
D.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
E.
hasBuiltEnvironment
Indicates that an entity possesses, contains, or is associated with human-made physical structures or infrastructure in its environment.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c261904819086910898071f3629 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.