Triple
T22625474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jisr az-Zarqa local council |
E558403
|
entity |
| Predicate | hasCoastalStatus |
P32974
|
FINISHED |
| Object | coastal municipality |
—
|
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 municipality | Statement: [Jisr az-Zarqa local council, hasCoastalStatus, coastal municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalStatus Context triple: [Jisr az-Zarqa local council, hasCoastalStatus, coastal municipality]
-
A.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
B.
hasCoastalSection
Indicates that a geographic entity includes at least one section of land that directly borders a sea or ocean.
-
C.
hasCoastlineDesignation
chosen
Indicates that a geographic area’s coastline has been assigned a specific official classification or status.
-
D.
hasCoastalCharacteristic
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
-
E.
isCoastalArea
Indicates that a given area is located along or directly adjacent to a sea or ocean 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3d55b081908930ebff4372154f |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:01 p.m.