Triple
T24572718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurelian Walls segment near Porta Maggiore |
E608003
|
entity |
| Predicate | laterModifiedUnder |
P152912
|
FINISHED |
| Object | Emperor Probus |
E725487
|
NE 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: Emperor Probus | Statement: [Aurelian Walls segment near Porta Maggiore, laterModifiedUnder, Emperor Probus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterModifiedUnder Context triple: [Aurelian Walls segment near Porta Maggiore, laterModifiedUnder, Emperor Probus]
-
A.
laterModifiedIn
Indicates that one entity was modified at a later time than another entity within the same context or sequence.
-
B.
laterModifiedTo
Indicates that an entity was changed or updated at a later time into another specified form or state.
-
C.
laterModifiedInPeriod
Indicates that one entity was modified at a later time than another entity within the same defined time period.
-
D.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
E.
eraOfSubsequentModification
chosen
Indicates the time period during which a later change or modification to something took place.
- F. None of above.
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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9269360819090c44f4483c3533c |
completed | April 30, 2026, 12:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10047462588190980ab36a8fbf1e8e |
completed | May 22, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:28 a.m.