Triple
T21713093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hanged Man |
E535952
|
entity |
| Predicate | reversedMeaning |
P63853
|
FINISHED |
| Object | resistance to change |
—
|
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: resistance to change | Statement: [The Hanged Man, reversedMeaning, resistance to change]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reversedMeaning Context triple: [The Hanged Man, reversedMeaning, resistance to change]
-
A.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
B.
reverseInscriptionMeaning
chosen
Indicates that the inscription’s meaning is the reverse or opposite of the usual or expected interpretation.
-
C.
reverseMottoTranslation
Indicates that one entity is a translation of another entity’s motto, rendered in the reverse language direction (from the target language back to the source language).
-
D.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
E.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb53573a08190ad73576d27e8094f |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.