Triple
T63335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of National Drug Control Policy |
E1258
|
entity |
| Predicate | hasHead |
P981
|
FINISHED |
| Object | Director of the Office of National Drug Control 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: Director of the Office of National Drug Control Policy | Statement: [Office of National Drug Control Policy, hasHead, Director of the Office of National Drug Control Policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHead Context triple: [Office of National Drug Control Policy, hasHead, Director of the Office of National Drug Control Policy]
-
A.
heads
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
-
B.
hasLeader
chosen
Indicates that one entity serves as the leader or head of another entity.
-
C.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
-
D.
hasBeard
Indicates that one entity possesses or displays a beard.
-
E.
hasMarker
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.