Triple
T18732238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of the City of London |
E458060
|
entity |
| Predicate | includesTransformation |
P133346
|
FINISHED |
| Object | fromRomanTownToMedievalCity |
—
|
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: fromRomanTownToMedievalCity | Statement: [History of the City of London, includesTransformation, fromRomanTownToMedievalCity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTransformation Context triple: [History of the City of London, includesTransformation, fromRomanTownToMedievalCity]
-
A.
usesTransformation
Indicates that one entity applies or relies on a specific transformation process, method, or function to operate on or convert another entity.
-
B.
hasTransformation
Indicates that one entity changes or is converted into another entity, capturing a transformation process or result.
-
C.
hasTransformationType
Indicates that an entity undergoes or is associated with a specific kind or category of transformation.
-
D.
canTransform
Indicates that one entity is capable of being changed or converted into another entity or state.
-
E.
includesTransformFault
Indicates that one geological feature or region contains or is associated with a transform fault within its extent.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d7854748190b66c4aaadfd67f29 |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:51 a.m.