Triple
T7527737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochester, Kent, England |
E177936
|
entity |
| Predicate | hasRomanHistory |
P57949
|
FINISHED |
| Object | site of Roman settlement Durobrivae |
—
|
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: site of Roman settlement Durobrivae | Statement: [Rochester, Kent, England, hasRomanHistory, site of Roman settlement Durobrivae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanHistory Context triple: [Rochester, Kent, England, hasRomanHistory, site of Roman settlement Durobrivae]
-
A.
hasRomanMonument
chosen
Indicates that one entity possesses, contains, or includes a monument of Roman origin or style.
-
B.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
-
C.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
D.
usedInRomanPeriodFor
Indicates that something served a particular function, purpose, or application during the Roman period.
-
E.
hasHistoricalPolity
Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81cc5748190818443c48c9e3114 |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.