Triple
T32541401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feriae Latinae |
E831721
|
entity |
| Predicate | requiredPresenceOf |
P18895
|
FINISHED |
| Object | Roman magistrates |
—
|
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: Roman magistrates | Statement: [Feriae Latinae, requiredPresenceOf, Roman magistrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredPresenceOf Context triple: [Feriae Latinae, requiredPresenceOf, Roman magistrates]
-
A.
requiresPresence
chosen
Indicates that one entity’s existence, operation, or validity depends on another entity being present or available.
-
B.
requiresPresenceIn
Indicates that one entity’s existence, validity, or operation depends on another entity being physically or contextually present.
-
C.
requiredOn
Indicates that one entity must exist, be present, or be fulfilled on a specific other entity, date, or condition as a mandatory requirement.
-
D.
requestedPresenceOf
Indicates that one entity has asked or required another entity to be present at a specific place, time, or event.
-
E.
meetsInPresenceOf
Indicates that two or more entities meet or interact while another specified entity is present as a witness, chaperone, or contextual participant.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 1, 2026, 1:02 a.m.