Triple
T19703277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BarCamp |
E473148
|
entity |
| Predicate | agendaSetBy |
P137002
|
FINISHED |
| Object | attendees |
—
|
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: attendees | Statement: [BarCamp, agendaSetBy, attendees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agendaSetBy Context triple: [BarCamp, agendaSetBy, attendees]
-
A.
agendaItem
Indicates that something is an item or entry on a planned agenda or schedule of topics to be addressed.
-
B.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
C.
calendarModification
Indicates a change made to a calendar, such as adding, removing, or updating scheduled events or time slots.
-
D.
calendarAssociation
Indicates a relationship where one entity is linked to or associated with a particular calendar or calendaring context (such as events, schedules, or timeframes).
-
E.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
- 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.