Triple
T2543004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porthmadog |
E57826
|
entity |
| Predicate | hasMaritimeHistory |
P20564
|
FINISHED |
| Object | slate shipping |
—
|
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: slate shipping | Statement: [Porthmadog, hasMaritimeHistory, slate shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeHistory Context triple: [Porthmadog, hasMaritimeHistory, slate shipping]
-
A.
hasMaritimeHeritage
chosen
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
B.
hasMaritimeMuseum
Indicates that one entity possesses, hosts, or includes a maritime museum as part of its features or facilities.
-
C.
hasNavalFacility
Indicates that one entity possesses, hosts, or contains a naval facility (such as a naval base, port, or installation) associated with it.
-
D.
hasNotableSea
Indicates that an entity is associated with or contains a sea that is considered notable or significant.
-
E.
hasRiverPortHistory
Indicates that an entity has a historical association with functioning as a river port or hosting river port activities.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bf6cac819083a9ab9d041d8641 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.