Triple
T9608261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate chamber in Palazzo Madama |
E232029
|
entity |
| Predicate | mainUserGroup |
P17010
|
FINISHED |
| Object | Italian senators |
—
|
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: Italian senators | Statement: [Senate chamber in Palazzo Madama, mainUserGroup, Italian senators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainUserGroup Context triple: [Senate chamber in Palazzo Madama, mainUserGroup, Italian senators]
-
A.
primaryUserGroup
chosen
Indicates the main or default user group to which a user is primarily assigned or associated.
-
B.
secondaryUserGroup
Indicates a relationship where a user is associated with an additional, non-primary group that supplements their main group membership.
-
C.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
D.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
E.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a8300e48190bef51f61febc061d |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.