Triple
T1182615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASEAN Regional Forum |
E25171
|
entity |
| Predicate | chairmanshipRotates |
P24978
|
FINISHED |
| Object | annually |
—
|
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: annually | Statement: [ASEAN Regional Forum, chairmanshipRotates, annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chairmanshipRotates Context triple: [ASEAN Regional Forum, chairmanshipRotates, annually]
-
A.
chairperson
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
-
B.
chairingSystem
Indicates that an entity is responsible for leading, overseeing, or presiding over a particular system or organized structure.
-
C.
hasChairmanTitle
Indicates that an entity holds the position or official title of chairman in relation to another entity or organization.
-
D.
currentChairStartDate
Indicates the date on which the person’s current term as chair officially began.
-
E.
hasFormerChairperson
Indicates that an entity previously held the role of chairperson of another entity, but no longer occupies that position.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd35fb888190adf1e5d0615fa725 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc6d5b7881908091e40c8695ef53 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:45 p.m.