Triple
T21133541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquinnah Cultural Landscape |
E520750
|
entity |
| Predicate | hasLandType |
P940
|
FINISHED |
| Object | coastal environment |
—
|
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: coastal environment | Statement: [Aquinnah Cultural Landscape, hasLandType, coastal environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandType Context triple: [Aquinnah Cultural Landscape, hasLandType, coastal environment]
-
A.
hasLandComponent
Indicates that something includes, consists of, or is associated with a land-based part or portion as one of its components.
-
B.
hasLandStatus
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
C.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
D.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
E.
isInLand
Indicates that one entity is located within the geographical boundaries of a land area or territory 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235847948190984c7009ca7f6189 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.