Triple
T29090430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romula |
E734837
|
entity |
| Predicate | placeOfSignificantCommemoration |
P115845
|
FINISHED |
| Object | Felix Romuliana |
—
|
NE NERFINISHED |
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: Felix Romuliana | Statement: [Romula, placeOfSignificantCommemoration, Felix Romuliana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfSignificantCommemoration Context triple: [Romula, placeOfSignificantCommemoration, Felix Romuliana]
-
A.
placeOfEventCommemorated
Indicates the location where the event being commemorated actually took place.
-
B.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
C.
memorialSiteFor
chosen
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
-
D.
hasCommemorativeStructure
Indicates that one entity possesses or is associated with a physical structure created to honor, remember, or commemorate another entity or event.
-
E.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 11:04 a.m.