Triple
T24556114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvey Bullock |
E607519
|
entity |
| Predicate | ultimatelySidesWith |
P70539
|
FINISHED |
| Object | law and order |
—
|
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: law and order | Statement: [Harvey Bullock, ultimatelySidesWith, law and order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimatelySidesWith Context triple: [Harvey Bullock, ultimatelySidesWith, law and order]
-
A.
politicalSide
Indicates the political alignment or ideological position that one entity holds in relation to political spectra or groupings.
-
B.
politicalBlocOnOneSide
Indicates that the entities belong to the same political bloc or coalition aligned on one side of a political division or conflict.
-
C.
partyAlignment
chosen
Indicates the political party or faction with which an entity is formally or informally affiliated or aligned.
-
D.
politicalBlocOnOtherSide
Indicates that one political bloc is positioned in opposition to, or on the opposing side of, another political bloc within a political context.
-
E.
unionSide
Indicates that an entity is aligned with, represents, or acts on behalf of a labor union in a labor-related relationship or context.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f2af7c8190904f247ef29121d0 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.