Triple
T25014381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nahoon River |
E626084
|
entity |
| Predicate | hasBankLandUse |
P37665
|
FINISHED |
| Object | residential areas |
—
|
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: residential areas | Statement: [Nahoon River, hasBankLandUse, residential areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBankLandUse Context triple: [Nahoon River, hasBankLandUse, residential areas]
-
A.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
B.
hasLandmarkOnBank
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
C.
servesLandUseType
Indicates that one entity functions to support, accommodate, or provide services for a specified land use type.
-
D.
beneficiaryLandUse
Indicates that one entity benefits from or is the intended beneficiary of a particular use or utilization of land by another entity.
-
E.
landUseIncludes
chosen
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:06 a.m.