Triple
T7460575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia boards |
E176235
|
entity |
| Predicate | suspend |
P6070
|
FINISHED |
| Object | professional licenses in the District of Columbia |
—
|
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: professional licenses in the District of Columbia | Statement: [District of Columbia boards, suspend, professional licenses in the District of Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suspend Context triple: [District of Columbia boards, suspend, professional licenses in the District of Columbia]
-
A.
suspension
chosen
Indicates the temporary removal or halting of a privilege, activity, or status for an entity, often as a consequence or precaution.
-
B.
halted
Indicates that an ongoing process, action, or movement has been stopped or brought to an end.
-
C.
suspendedIn
Indicates that one entity is held or maintained within another medium or environment without settling or separating.
-
D.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
-
E.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
- 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.