Triple
T23632721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbigland Bay |
E583658
|
entity |
| Predicate | shorelineFeatureOf |
P5879
|
FINISHED |
| Object | Arbigland estate |
—
|
NE NERFINISHED |
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: Arbigland estate | Statement: [Arbigland Bay, shorelineFeatureOf, Arbigland estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineFeatureOf Context triple: [Arbigland Bay, shorelineFeatureOf, Arbigland estate]
-
A.
coastlineFeature
Indicates that a geographic entity is a specific type of feature located along or forming part of a coastline.
-
B.
shorelineCharacteristic
Indicates the specific physical or environmental qualities that describe the nature or condition of a shoreline in relation to another entity.
-
C.
containsCoastalFeature
chosen
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
-
D.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
E.
hasLongShoreline
Indicates that an entity possesses an extensive or unusually long shoreline relative to typical cases.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e90a6881909f19b2446f9d54f0 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:47 p.m.