Triple
T21054259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lough Swilly |
E518667
|
entity |
| Predicate | wasBritishTreatyPortUntil |
P142658
|
FINISHED |
| Object | 1938 |
—
|
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: 1938 | Statement: [Lough Swilly, wasBritishTreatyPortUntil, 1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBritishTreatyPortUntil Context triple: [Lough Swilly, wasBritishTreatyPortUntil, 1938]
-
A.
servedAsMainSeaportUntil
Indicates that an entity functioned as the primary seaport for another entity up to a specified point in time.
-
B.
treatyStatusOfPort
Indicates the legal status of a port as defined or regulated by a specific treaty or international agreement.
-
C.
wasUnderTrusteeshipOf
Indicates that one entity was administered, overseen, or managed under the legal or formal trusteeship authority of another entity.
-
D.
broughtUnderBritishCrown
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
-
E.
governedUnderSuzeraintyOf
Indicates that one entity exercises suzerain authority over another, which retains limited internal autonomy but is politically subordinate in key matters such as foreign policy or defense.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7e087c81908712ddc63e8b1e6c |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:36 p.m.