Triple
T26708928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiroxiphia |
E673355
|
entity |
| Predicate | cooperativeDisplayParticipants |
P107033
|
FINISHED |
| Object | multiple males |
—
|
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: multiple males | Statement: [Chiroxiphia, cooperativeDisplayParticipants, multiple males]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperativeDisplayParticipants Context triple: [Chiroxiphia, cooperativeDisplayParticipants, multiple males]
-
A.
coalitionParticipants
chosen
Indicates that certain entities are members or participants in the same coalition.
-
B.
previousParticipantsFormat
Indicates that there is a specific way or structure in which information about prior participants is represented or recorded.
-
C.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
D.
secondaryParticipants
Indicates that certain entities participate in an event or activity in a supporting or non-primary role alongside the main participants.
-
E.
vowOfParticipants
Indicates that certain participants formally promise or commit themselves to a specified action, condition, or relationship.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617bcfbb0819092a1334dc7553a97 |
completed | May 2, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:35 a.m.