Triple
T4409565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Old House |
E94817
|
entity |
| Predicate | associatedRegionDepicted |
P12445
|
FINISHED |
| Object | northern England |
—
|
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: northern England | Statement: [The Old House, associatedRegionDepicted, northern England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRegionDepicted Context triple: [The Old House, associatedRegionDepicted, northern England]
-
A.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
B.
represented region
Indicates that one entity serves as a symbolic or formal depiction of a specific geographic or spatial area.
-
C.
regionallyAssociatedWith
chosen
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
arealRegion
Indicates that something occupies or pertains to a specific two-dimensional geographic or spatial area.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3548e24d08190a38c0bcd4b6ad571 |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.