Triple
T19703278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BarCamp |
E473148
|
entity |
| Predicate | sessionsLedBy |
P137003
|
FINISHED |
| Object | participants |
—
|
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: participants | Statement: [BarCamp, sessionsLedBy, participants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sessionsLedBy Context triple: [BarCamp, sessionsLedBy, participants]
-
A.
sessionConvenedBy
Indicates that a particular session is organized, initiated, or formally brought together by a specified agent or authority.
-
B.
sessionOf
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
-
C.
seriesLeader
Indicates that one entity serves as the primary leader, head, or main responsible figure for a particular series involving another entity.
-
D.
conferenceCoachedIn
Indicates that a person provided coaching or guidance during a specific conference.
-
E.
conferenceServed
Indicates that a particular conference provided services, resources, or support to a specified entity (such as attendees, organizations, or events).
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b8707081908fbf96c989d2d52d |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.