Triple
T26082410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Colson |
E657880
|
entity |
| Predicate | concernsConduct |
P11116
|
FINISHED |
| Object | political sabotage activities |
—
|
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: political sabotage activities | Statement: [United States v. Colson, concernsConduct, political sabotage activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsConduct Context triple: [United States v. Colson, concernsConduct, political sabotage activities]
-
A.
concernsTypeOfConduct
Indicates that something is about or relates specifically to a particular type or category of conduct or behavior.
-
B.
conducts
Indicates that an entity organizes, directs, or carries out an activity, operation, or process involving another entity.
-
C.
concern
chosen
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
D.
concernsPoliceConduct
Indicates that the matter involves or pertains to the behavior, actions, or practices of police officers or law enforcement agencies.
-
E.
subjectOfConcernFor
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 26, 2026, 7:39 p.m.