Triple
T28167005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poèmes pour la paix |
E715353
|
entity |
| Predicate | expressesConviction |
P4750
|
FINISHED |
| Object | humanist convictions |
—
|
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: humanist convictions | Statement: [Poèmes pour la paix, expressesConviction, humanist convictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressesConviction Context triple: [Poèmes pour la paix, expressesConviction, humanist convictions]
-
A.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
-
B.
reasonForConviction
Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
-
C.
initialConviction
Indicates the original judgment or decision of guilt assigned to an entity before any appeals, modifications, or subsequent legal actions.
-
D.
convictionJurisdiction
Indicates the legal authority or geographic area under whose jurisdiction a conviction was issued.
-
E.
expresses
chosen
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6423402bc8190ba5aea2c7d6bd984 |
completed | May 2, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:10 p.m.