Triple
T32519617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Routing Working Group |
E831145
|
entity |
| Predicate | holdsSessionAt |
P30503
|
FINISHED |
| Object | RIPE Meetings |
—
|
NE NERFINISHED |
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: RIPE Meetings | Statement: [Routing Working Group, holdsSessionAt, RIPE Meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsSessionAt Context triple: [Routing Working Group, holdsSessionAt, RIPE Meetings]
-
A.
heldSessionsIn
chosen
Indicates that an entity organized or conducted one or more sessions, meetings, or events at a specified location or venue.
-
B.
holdsAt
Indicates that a particular condition or fluent is true and persists at a specified point in time.
-
C.
holdsService
Indicates that one entity provides, maintains, or is responsible for a particular service for another entity or context.
-
D.
inSessionDuring
Indicates that an entity is actively engaged in or part of a session throughout a specified time period.
-
E.
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).
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1 a.m.