Triple
T389428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeddah |
E8848
|
entity |
| Predicate | coastalFeature |
P5879
|
FINISHED |
| Object | coral reefs off the Red Sea 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: coral reefs off the Red Sea coast | Statement: [Jeddah, coastalFeature, coral reefs off the Red Sea coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalFeature Context triple: [Jeddah, coastalFeature, coral reefs off the Red Sea coast]
-
A.
coastlineFeature
Indicates that a geographic entity is a specific type of feature located along or forming part of a coastline.
-
B.
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.
-
C.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
-
D.
flowsAlongCoastOf
Indicates that something, typically a body of water or current, moves in a path that follows and runs adjacent to a coastline.
-
E.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5bdc848190826701590070497b |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.