Triple
T27831412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branwell House, Penzance |
E703107
|
entity |
| Predicate | situatedInTown |
P163391
|
FINISHED |
| Object | Penzance |
—
|
NE NERFINISHED |
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: Penzance | Statement: [Branwell House, Penzance, situatedInTown, Penzance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedInTown Context triple: [Branwell House, Penzance, situatedInTown, Penzance]
-
A.
operatesInTown
Indicates that an entity conducts its activities, business, or operations within a particular town.
-
B.
locatedInPlannedTown
Indicates that an entity is situated within the boundaries of a town that has been deliberately planned or designed rather than having developed organically.
-
C.
usedInTown
Indicates that something is utilized, applied, or functions within the context or boundaries of a particular town.
-
D.
locatedInWaterfrontTown
Indicates that the subject is situated within a town that is directly adjacent to or closely associated with a body of water, such as a sea, lake, or river.
-
E.
isInteriorTownOf
Indicates that one town is located within the interior region of, and is administratively or geographically associated with, a larger area or jurisdiction.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6389be24481909a1daa27266833d8 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:56 p.m.