Triple
T10894519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Suicide |
E257271
|
entity |
| Predicate | titleExplainsConcept |
P4542
|
FINISHED |
| Object | revolutionary suicide |
—
|
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: revolutionary suicide | Statement: [Revolutionary Suicide, titleExplainsConcept, revolutionary suicide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleExplainsConcept Context triple: [Revolutionary Suicide, titleExplainsConcept, revolutionary suicide]
-
A.
titleMeaning
chosen
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
B.
titleIIPurpose
Indicates that something states or defines the intended purpose or objective of Title II within a legal or regulatory framework.
-
C.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
D.
titlePhrase
Indicates that one entity is a phrase functioning as the title or name of another entity.
-
E.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d0153408190bcba2d9b03d78804 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.