Triple
T27291793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ksar Sghir |
E688647
|
entity |
| Predicate | nearbyPortComplex |
P86796
|
FINISHED |
| Object | Tanger-Med |
—
|
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: Tanger-Med | Statement: [Ksar Sghir, nearbyPortComplex, Tanger-Med]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyPortComplex Context triple: [Ksar Sghir, nearbyPortComplex, Tanger-Med]
-
A.
nearbyPortFacility
chosen
Indicates that one entity is located close to or in the immediate vicinity of a port facility.
-
B.
nearbyCityOrPort
Indicates that one location is geographically close to a city or port, typically within a short travel distance.
-
C.
oftenLocatedNear
Indicates that one entity is frequently found in close physical proximity to another entity.
-
D.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
E.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 11:16 a.m.