Triple
T2587304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Colony |
E58033
|
entity |
| Predicate | landSystem |
P34249
|
FINISHED |
| Object | manorial estates in Hudson Valley |
—
|
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 estates in Hudson Valley | Statement: [New York Colony, landSystem, manorial estates in Hudson Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landSystem Context triple: [New York Colony, landSystem, manorial estates in Hudson Valley]
-
A.
landPolicy
Indicates a relationship where an authority defines or applies rules governing the ownership, use, management, or distribution of land.
-
B.
landTenure
chosen
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
C.
landholdings
Indicates the extent or collection of land owned, controlled, or held by an entity.
-
D.
landComponent
Indicates that one entity is a physical land portion or segment that forms part of a larger land area or land-related whole.
-
E.
landholderIn
Indicates that one entity holds legal or recognized ownership or tenancy rights over land located within the jurisdiction or bounds of another entity.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd3f8a3888190889c537e6df07305 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.