Triple
T16099681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Lubbock Cemetery |
E390581
|
entity |
| Predicate | hasLandUseCategory |
P43475
|
FINISHED |
| Object | cemetery 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: cemetery land | Statement: [City of Lubbock Cemetery, hasLandUseCategory, cemetery land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandUseCategory Context triple: [City of Lubbock Cemetery, hasLandUseCategory, cemetery land]
-
A.
hasLandUseCharacter
chosen
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
B.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
C.
hasTertiaryLandUse
Indicates that an entity is associated with a third-level or additional land use classification beyond its primary and secondary land uses.
-
D.
hasLandUsePressure
Indicates that an area or entity is subject to demands or stresses from human or other uses of land that may affect its condition or availability.
-
E.
beneficiaryLandUse
Indicates that one entity benefits from or is the intended beneficiary of a particular use or utilization of land by 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6756948190a7f5ecb375e59701 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.