Triple
T19115670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advisory Neighborhood Commissions in Washington, D.C. |
E467900
|
entity |
| Predicate | meetingsOpenTo |
P134487
|
FINISHED |
| Object | general public |
—
|
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: general public | Statement: [Advisory Neighborhood Commissions in Washington, D.C., meetingsOpenTo, general public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingsOpenTo Context triple: [Advisory Neighborhood Commissions in Washington, D.C., meetingsOpenTo, general public]
-
A.
meetingsAre
Indicates that certain entities function as or are classified as meetings in relation to one another.
-
B.
meetsBy
Indicates that one entity encounters or comes together with another entity, typically at a specific time or place.
-
C.
meetsVia
Indicates that two entities come into contact or interact with each other through a specified intermediary medium, channel, or mechanism.
-
D.
meetingsWere
Indicates that one or more meetings occurred or were held between the referenced entities.
-
E.
hasMeeting
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or place.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39736588190b80ddef77101641a |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.