Triple
T31959551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voltumna |
E815996
|
entity |
| Predicate | meetingFunction |
P173487
|
FINISHED |
| Object | presided over federal assemblies at Fanum Voltumnae |
—
|
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: presided over federal assemblies at Fanum Voltumnae | Statement: [Voltumna, meetingFunction, presided over federal assemblies at Fanum Voltumnae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingFunction Context triple: [Voltumna, meetingFunction, presided over federal assemblies at Fanum Voltumnae]
-
A.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
B.
meetingContext
Indicates the situational setting, circumstances, or background conditions in which a meeting takes place.
-
C.
meeting
Indicates that two or more entities come together at the same time and place for discussion, decision-making, or coordinated activity.
-
D.
meetingLevel
Indicates the degree or intensity of interaction or engagement between participants in a meeting or meeting-like context.
-
E.
meetingPartner
Indicates that two entities are participants in the same meeting, standing in a mutual partner or counterpart relationship within that meeting.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:08 a.m.