Triple
T15759933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horton Kirby |
E382068
|
entity |
| Predicate | hasAgriculturalLandNearby |
P93890
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Horton Kirby, hasAgriculturalLandNearby, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgriculturalLandNearby Context triple: [Horton Kirby, hasAgriculturalLandNearby, true]
-
A.
hasNearbyAgriculturalActivity
chosen
Indicates that an entity is located close enough to agricultural operations or land use for those activities to be considered relevant or influential to it.
-
B.
hasNearbyPublicLand
Indicates that one entity is located close to an area of public land, such as parks, reserves, or other publicly accessible open spaces.
-
C.
hasAgriculturalCharacter
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
-
D.
hasRuralArea
Indicates that an entity includes, is associated with, or contains a countryside or sparsely populated geographic area.
-
E.
locatedInAgriculturalRegion
Indicates that an entity is situated within a region primarily characterized by agricultural activities or land use.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b35ea48190a758ee76a57b5451 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.