Triple
T20741327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cramond Roman Fort |
E510447
|
entity |
| Predicate | reoccupiedInCentury |
P47367
|
FINISHED |
| Object | 3rd century |
—
|
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: 3rd century | Statement: [Cramond Roman Fort, reoccupiedInCentury, 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reoccupiedInCentury Context triple: [Cramond Roman Fort, reoccupiedInCentury, 3rd century]
-
A.
reestablishedInCentury
Indicates that an entity, previously established and then discontinued or disrupted, was re-founded or restored during a specified century.
-
B.
reacquiredInCentury
Indicates that an entity was reacquired during a specified century.
-
C.
wasRepopulatedInCentury
chosen
Indicates that a place or region, previously depopulated or abandoned, became populated again during the specified century.
-
D.
reorganizedInCentury
Indicates that an entity underwent a significant reorganization or structural change during the specified century.
-
E.
settledInCentury
Indicates that an entity’s act of settling or establishment occurred during a specified century.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20e76ac8190985203b2c17aca14 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:32 p.m.