Triple
T7460581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia boards |
E176235
|
entity |
| Predicate | advise |
P488
|
FINISHED |
| Object | District of Columbia government on regulatory policy |
—
|
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: District of Columbia government on regulatory policy | Statement: [District of Columbia boards, advise, District of Columbia government on regulatory policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advise Context triple: [District of Columbia boards, advise, District of Columbia government on regulatory policy]
-
A.
advises
chosen
Indicates that one entity provides guidance, recommendations, or counsel to another entity.
-
B.
advisorOf
Indicates that one entity serves as an advisor, providing guidance or counsel, to another entity.
-
C.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
D.
encourages
Indicates actively motivating, supporting, or giving confidence to another entity to pursue an action, behavior, or state.
-
E.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d525708190b7838e07ac2fbe1f |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.