Triple
T13335288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cranford House (site of former manor house) |
E317673
|
entity |
| Predicate | marksLocationOf |
P109072
|
FINISHED |
| Object | former manor house in Cranford |
—
|
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: former manor house in Cranford | Statement: [Cranford House (site of former manor house), marksLocationOf, former manor house in Cranford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksLocationOf Context triple: [Cranford House (site of former manor house), marksLocationOf, former manor house in Cranford]
-
A.
locationOfMark
Indicates that one entity is the place or position where a particular mark is found or applied.
-
B.
labelLocation
Indicates that a label or identifier is associated with a specific spatial or geographic location.
-
C.
marksMeetingPointOf
Indicates that something designates or identifies the specific location where two or more entities meet or converge.
-
D.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
E.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cff44e08190b9583baf0b626e42 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99073e4708190843bda3a1ae78f43 |
completed | April 11, 2026, 12:06 a.m. |
Created at: April 9, 2026, 9:30 p.m.