Triple
T4665318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotts Head |
E102830
|
entity |
| Predicate | coastalOrientation |
P45094
|
FINISHED |
| Object | east-facing coast |
—
|
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: east-facing coast | Statement: [Scotts Head, coastalOrientation, east-facing coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalOrientation Context triple: [Scotts Head, coastalOrientation, east-facing coast]
-
A.
coastOrientation
chosen
Indicates the directional alignment or facing direction of a coastline relative to the cardinal or geographic axes.
-
B.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
-
C.
coastOff
Indicates that one entity is located just off the coast of another, typically in nearby offshore waters rather than directly on the shoreline.
-
D.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
E.
basedOnCoast
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.