Triple
T11057284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C meetings |
E261406
|
entity |
| Predicate | oftenHeldAs |
P97558
|
FINISHED |
| Object | recurring meetings |
—
|
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: recurring meetings | Statement: [W3C meetings, oftenHeldAs, recurring meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenHeldAs Context triple: [W3C meetings, oftenHeldAs, recurring meetings]
-
A.
oftenHeldOn
Indicates that an event or activity typically takes place on a particular date, day, or time.
-
B.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
C.
oftenHeldToBe
Indicates that something is frequently regarded, considered, or believed to be a certain way by many people or in many contexts.
-
D.
typicallyHeldIn
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
E.
qualificationHeld
Indicates that an entity possesses or has obtained a particular qualification or credential.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a2404c819090cb0825a67a64fa |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.