Triple
T32806082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERO |
E839022
|
entity |
| Predicate | usesContentDescriptors |
P139410
|
FINISHED |
| Object | violence |
—
|
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: violence | Statement: [CERO, usesContentDescriptors, violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesContentDescriptors Context triple: [CERO, usesContentDescriptors, violence]
-
A.
contentDescriptor
Indicates that something provides a description or characterization of the content of another entity (such as a resource, item, or work).
-
B.
typicalContentDescriptors
chosen
Indicates the usual or characteristic types of content or attributes that are commonly associated with an entity.
-
C.
contentDescriptorScope
Indicates the contextual scope or domain within which a particular content descriptor is intended to apply.
-
D.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
-
E.
hasNumberOfFeaturesDescribed
Indicates that an entity is associated with a specific count of its features that have been described.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 1:15 a.m.