Triple
T3901956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Philipsburg Manor |
E90514
|
entity |
| Predicate | propertyTypeControlled |
P51437
|
FINISHED |
| Object | manorial estate |
—
|
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: manorial estate | Statement: [Lord of Philipsburg Manor, propertyTypeControlled, manorial estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyTypeControlled Context triple: [Lord of Philipsburg Manor, propertyTypeControlled, manorial estate]
-
A.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another entity.
-
B.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
C.
typeOfPropertyManaged
chosen
Indicates the specific category or kind of property that an entity is responsible for managing.
-
D.
propertyTypeMix
Indicates that an entity involves or consists of a combination of different types of properties rather than a single uniform property type.
-
E.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.