Triple
T30807919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostian Road |
E784555
|
entity |
| Predicate | hasModernRemnants |
P194019
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ostian Road, hasModernRemnants, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernRemnants Context triple: [Ostian Road, hasModernRemnants, yes]
-
A.
hasModernLegacyIn
Indicates that something continues to exert influence, relevance, or impact within a modern context, domain, or location.
-
B.
hasModernRepresentatives
Indicates that an entity has current or contemporary examples, members, or instances that represent it in the modern era.
-
C.
hasModernPeriod
Indicates that an entity possesses, is associated with, or falls within a defined modern historical or stylistic period.
-
D.
isYoungerRemnantOf
Indicates that one entity is the surviving, younger portion or successor of another entity that existed earlier and has largely disappeared or transformed.
-
E.
hasModernReflex
Indicates that an older or historical form has a corresponding modern descendant or outcome in a contemporary language stage.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: April 29, 2026, 8:43 p.m.