Triple
T35555455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Härkeberga rectory collections |
E1027479
|
entity |
| Predicate | physicalLocationType |
P104071
|
FINISHED |
| Object | historic rectory building |
—
|
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: historic rectory building | Statement: [Härkeberga rectory collections, physicalLocationType, historic rectory building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalLocationType Context triple: [Härkeberga rectory collections, physicalLocationType, historic rectory building]
-
A.
hasPhysicalLocationType
chosen
Indicates that an entity is associated with a specific kind or category of physical location (e.g., building type, facility type, or place type).
-
B.
isPhysicalLocation
Indicates that one entity serves as a physical, real-world place or site associated with another entity.
-
C.
emplacementType
Indicates the specific manner or configuration in which something is positioned, installed, or set in place relative to its surroundings.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
subjectLocationType
Indicates the type or category of location associated with the subject in the relationship.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.