Triple
T36158620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hythe, Kent |
E1045810
|
entity |
| Predicate | roleInCinquePorts |
P50907
|
FINISHED |
| Object | one of the original Cinque Ports |
—
|
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: one of the original Cinque Ports | Statement: [Hythe, Kent, roleInCinquePorts, one of the original Cinque Ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCinquePorts Context triple: [Hythe, Kent, roleInCinquePorts, one of the original Cinque Ports]
-
A.
statusWithinCinquePorts
chosen
Indicates that an entity holds a particular legal or administrative status that applies specifically within the jurisdiction of the Cinque Ports.
-
B.
wasBritishTreatyPortUntil
Indicates that a place functioned as a British-controlled treaty port up to a specified end date.
-
C.
roleAtTrafalgar
Indicates the specific role, position, or function an entity held during the Battle of Trafalgar.
-
D.
roleAtPortOfBalboa
Indicates that an entity holds or performs a specific role or function at the Port of Balboa.
-
E.
partyRoleOfUnitedKingdom
Indicates that the specified role is one held by the United Kingdom as a party in a given agreement, event, or relationship.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a017590e01c8190b985bb50cc6cd605 |
completed | May 11, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_6a0175406b348190a5809b5f3497d46f |
completed | May 11, 2026, 6:20 a.m. |
Created at: May 3, 2026, 4:08 p.m.