Triple
T640008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oak Hill Conservation Land |
E16714
|
entity |
| Predicate | managementType |
P11436
|
FINISHED |
| Object | municipal conservation land |
—
|
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: municipal conservation land | Statement: [Oak Hill Conservation Land, managementType, municipal conservation land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementType Context triple: [Oak Hill Conservation Land, managementType, municipal conservation land]
-
A.
organizationTypeGoverned
Indicates that one entity governs or has authoritative control over a specific type or category of organization.
-
B.
managementApproach
Indicates the strategy, methods, or style used to direct, organize, and oversee the activities or resources of an entity or process.
-
C.
managementCompany
Indicates that one entity serves as the managing company responsible for overseeing or administering another entity.
-
D.
typeOfAdministration
chosen
Indicates the specific form or system of administration applied to or governing an entity.
-
E.
manager
Indicates that one entity holds a supervisory or administrative role with authority and responsibility over 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f00260081909d1a679182e23d10 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.