Triple
T10577427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kshamavani |
E249645
|
entity |
| Predicate | typicalGreetingMeaning |
P4600
|
FINISHED |
| Object | May all the evil that has been done be fruitless |
—
|
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: May all the evil that has been done be fruitless | Statement: [Kshamavani, typicalGreetingMeaning, May all the evil that has been done be fruitless]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGreetingMeaning Context triple: [Kshamavani, typicalGreetingMeaning, May all the evil that has been done be fruitless]
-
A.
typicalGreeting
chosen
Indicates the standard or commonly used way one entity greets another in a given context.
-
B.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
C.
basicMeaning
Indicates that one entity expresses or conveys the fundamental or core meaning of another entity.
-
D.
typicalKanjiMeaning
Indicates that one entity is the standard or commonly accepted meaning associated with a given kanji character.
-
E.
lettersMeaning
Indicates that a set of letters or characters represents, signifies, or conveys a particular meaning or message.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52756ff1c8190a85022748ca58ba5 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:38 p.m.