Triple
T30913821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Energy Forum |
E787525
|
entity |
| Predicate | organizesEventFrequency |
P148205
|
FINISHED |
| Object | biennial |
—
|
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: biennial | Statement: [International Energy Forum, organizesEventFrequency, biennial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizesEventFrequency Context triple: [International Energy Forum, organizesEventFrequency, biennial]
-
A.
isFrequentlyArrangedFor
Indicates that something is commonly or regularly organized, scheduled, or set up for a particular entity or purpose.
-
B.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
C.
開催頻度
chosen
Indicates how often an event or activity is held over a given period.
-
D.
eventTypeOrganized
Indicates that an entity organized or arranged a specific type or category of event.
-
E.
hasFestivalFrequency
Indicates how often a festival or recurring celebratory event takes place within a given time period.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 8:51 p.m.