Triple
T16687645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee Room 28 |
E405505
|
entity |
| Predicate | mayBeAccessibleTo |
P21488
|
FINISHED |
| Object | public observers |
—
|
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: public observers | Statement: [Committee Room 28, mayBeAccessibleTo, public observers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeAccessibleTo Context triple: [Committee Room 28, mayBeAccessibleTo, public observers]
-
A.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
-
B.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
C.
isAccessible
chosen
Indicates that one entity can be reached, used, or entered by another entity without obstruction or restriction.
-
D.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
-
E.
alsoAccessibleFrom
Indicates that a location, resource, or entity can be reached or obtained not only from one specified source or path but from an additional source or path as well.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea75df481909a7ebb9b2a9d0afd |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.