Triple
T3287695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unser |
E69021
|
entity |
| Predicate | conflictedBetween |
P47733
|
FINISHED |
| Object | duty as police chief |
—
|
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: duty as police chief | Statement: [Unser, conflictedBetween, duty as police chief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictedBetween Context triple: [Unser, conflictedBetween, duty as police chief]
-
A.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
B.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
C.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
D.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
E.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
- F. None of above. chosen
Provenance (4 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb058e00881908fdf0a23208860d4 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.