Triple
T3723088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libyan Sea |
E81683
|
entity |
| Predicate | isGeographicalEntity |
P51450
|
FINISHED |
| Object | marine region |
—
|
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: marine region | Statement: [Libyan Sea, isGeographicalEntity, marine region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeographicalEntity Context triple: [Libyan Sea, isGeographicalEntity, marine region]
-
A.
isPopulatedPlace
Indicates that the subject is a geographic location where people live or have lived, such as a city, town, village, or settlement.
-
B.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
C.
isPopulatedPlaceIn
Indicates that a populated place (such as a city, town, or village) is located within a specified larger geographic or administrative area.
-
D.
mapsToGeopoliticalEntity
Indicates a relationship where something is associated with, corresponds to, or is assigned to a specific geopolitical entity such as a country, region, or territory.
-
E.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
- F. None of above. chosen
Provenance (4 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9ea1688190b3b8414d77960e8f |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc48ec1a081909af0ff9f267c0ffe |
completed | March 8, 2026, 6:48 p.m. |
Created at: March 8, 2026, 3:34 p.m.