Triple
T32461837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seconda Categoria |
E829593
|
entity |
| Predicate | hasMultipleGroups |
P62241
|
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: [Seconda Categoria, hasMultipleGroups, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleGroups Context triple: [Seconda Categoria, hasMultipleGroups, yes]
-
A.
hasMultiple
chosen
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
B.
hasSecondaryUserGroup
Indicates that an entity is associated with an additional, non-primary user group beyond its main group.
-
C.
hasGroupStatus
Indicates that an entity possesses a particular status, role, or condition within a group or collective context.
-
D.
hasRepresentativeGroup
Indicates that an entity is associated with, or formally represented by, a specific group acting on its behalf.
-
E.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 12:57 a.m.