Triple
T34579231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Perl Conference |
E887842
|
entity |
| Predicate | typicalAttendeeRole |
—
|
GENERATED |
| Object | software engineer |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAttendeeRole Context triple: [The Perl Conference, typicalAttendeeRole, software engineer]
-
A.
attendanceRole
Indicates the specific capacity or role in which an entity participates in an attendance-related event or activity.
-
B.
typicalAdditionalRole
Indicates that an entity commonly or characteristically holds an extra role or function in addition to its primary one.
-
C.
typicalRole
chosen
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
D.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
E.
audienceRole
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
- F. None of above.
Provenance (1 batch)
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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.