Triple
T15812235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svetly |
E383382
|
entity |
| Predicate | hasMaritimeIndustry |
P76343
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [Svetly, hasMaritimeIndustry, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeIndustry Context triple: [Svetly, hasMaritimeIndustry, fishing]
-
A.
hasIndustrialPort
Indicates that a location possesses a port facility specifically equipped and used for industrial or commercial shipping activities.
-
B.
hasMaritimeConnection
chosen
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
C.
hasMaritimeHeritage
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
D.
hasNavalFacility
Indicates that one entity possesses, hosts, or contains a naval facility (such as a naval base, port, or installation) associated with it.
-
E.
hasMarineResource
Indicates that one entity possesses, contains, or is associated with a marine (ocean or sea-based) resource in relation to another entity.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52bbb888190b226567e84ced7e9 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.