Triple
T21219490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marche au supplice |
E522925
|
entity |
| Predicate | idéeFixeFunction |
P81043
|
FINISHED |
| Object | represents the beloved before the execution |
—
|
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: represents the beloved before the execution | Statement: [Marche au supplice, idéeFixeFunction, represents the beloved before the execution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: idéeFixeFunction Context triple: [Marche au supplice, idéeFixeFunction, represents the beloved before the execution]
-
A.
termFixedBy
Indicates that a term is determined, constrained, or made unchangeable by another entity or condition.
-
B.
functie
chosen
Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
-
C.
fixedTerm
Indicates that the relationship, agreement, or condition applies for a predetermined, non-variable duration of time.
-
D.
fixedBy
Indicates that one entity is repaired, corrected, or resolved through the action or intervention of another entity.
-
E.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73476d93481909c6c99dcc0b16123 |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:43 p.m.