Triple
T20075020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotary Club of Vienna |
E499837
|
entity |
| Predicate | typicalMeetingFormat |
P3082
|
FINISHED |
| Object | regular in-person 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: regular in-person meetings | Statement: [Rotary Club of Vienna, typicalMeetingFormat, regular in-person meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMeetingFormat Context triple: [Rotary Club of Vienna, typicalMeetingFormat, regular in-person meetings]
-
A.
meetingType
chosen
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
B.
conferenceFormat
Indicates the type or structure in which a conference is organized or conducted (e.g., in-person, virtual, hybrid, workshop-based).
-
C.
meetingPeriod
Indicates the time span or duration during which a meeting takes place.
-
D.
conferenceFormatUsed
Indicates that a particular conference is conducted using a specified format or modality (e.g., in-person, virtual, hybrid).
-
E.
meetingsAre
Indicates that certain entities function as or are classified as meetings in relation to one another.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643ab0448190ab18d013b72aaf32 |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.