Triple
T14877260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Portnoy |
E349898
|
entity |
| Predicate | hasVice |
P102734
|
FINISHED |
| Object | drug abuse |
—
|
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: drug abuse | Statement: [Jeff Portnoy, hasVice, drug abuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVice Context triple: [Jeff Portnoy, hasVice, drug abuse]
-
A.
hasViceChair
Indicates that an entity holds the role or position of vice chair in relation to another entity (such as an organization, committee, or group).
-
B.
hasViceMayor
Indicates that an entity holds the position of vice mayor for a given administrative or governmental body.
-
C.
vice
chosen
Indicates a relationship where one entity serves as the deputy, subordinate leader, or second-in-command to another entity in a hierarchical structure.
-
D.
hasViceChairTitle
Indicates that an entity holds the position or bears the formal title of vice chair in relation to another entity or organization.
-
E.
hadOutgoingVicePresidentPresent
Indicates that a current or former vice president attended or was present at the referenced event or occasion.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e4e4448190a8796573bc6d1069 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.