Triple
T13156900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advisory Committee in plenary session |
E312610
|
entity |
| Predicate | mayBeOpenTo |
P2556
|
FINISHED |
| Object | observers subject to rules |
—
|
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: observers subject to rules | Statement: [Advisory Committee in plenary session, mayBeOpenTo, observers subject to rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeOpenTo Context triple: [Advisory Committee in plenary session, mayBeOpenTo, observers subject to rules]
-
A.
initiallyOpenTo
Indicates that something starts out in an open state or condition at the beginning of a process, period, or interaction.
-
B.
isOpenTo
chosen
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
C.
alsoOpenOn
Indicates that a place, service, or resource is open or available during an additional specified time or on an additional specified day beyond its primary opening period.
-
D.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
E.
canBeOpenedBy
Indicates that one entity has the ability or permission to open another entity.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.