Triple
T634030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion Assembly |
E15982
|
entity |
| Predicate | hasGeneralAssembly |
P17337
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Orion Assembly, hasGeneralAssembly, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralAssembly Context triple: [Orion Assembly, hasGeneralAssembly, yes]
-
A.
hasPlenaryChamber
Indicates that an institution or governing body possesses a designated plenary chamber where all members can meet and deliberate together.
-
B.
heldCouncil
Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
-
C.
lastAssemblyMeeting
Indicates that a specified meeting is the most recent (or final) gathering of an assembly.
-
D.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
E.
convenesUnder
Indicates that an entity holds or conducts a meeting, session, or gathering under the authority, auspices, or framework of another entity or arrangement.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee4ee8481908ad45405e3f3835c |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49defe58c8190bd39ef47c9f660a7 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.