Triple
T29146953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent (early post-Roman phase) |
E738798
|
entity |
| Predicate | hadKeyPort |
P104217
|
FINISHED |
| Object | Richborough |
—
|
NE NERFINISHED |
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: Richborough | Statement: [Kent (early post-Roman phase), hadKeyPort, Richborough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadKeyPort Context triple: [Kent (early post-Roman phase), hadKeyPort, Richborough]
-
A.
hasKeyPort
chosen
Indicates that an entity possesses or is associated with a primary or main port used for connection, access, or communication.
-
B.
keyPort
Indicates that a port serves as a primary or central connection point in a system or network.
-
C.
hadKeyIssue
Indicates that an entity experienced a primary or critical problem related to a key aspect, factor, or component.
-
D.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
E.
hasKeyPassage
Indicates that one entity contains or includes a particularly important or central passage relevant 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66272f8548190b9274f67777b18b7 |
completed | May 2, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:40 a.m.