Triple
T27261401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mens Sana in Corpore Sano |
E687774
|
entity |
| Predicate | shortMeaning |
P92178
|
FINISHED |
| Object | healthy mind in a healthy body |
—
|
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: healthy mind in a healthy body | Statement: [Mens Sana in Corpore Sano, shortMeaning, healthy mind in a healthy body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortMeaning Context triple: [Mens Sana in Corpore Sano, shortMeaning, healthy mind in a healthy body]
-
A.
basicMeaning
chosen
Indicates that one entity expresses or conveys the fundamental or core meaning of another entity.
-
B.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
C.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
-
D.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
E.
typicalMeaning
Indicates that something represents the usual, characteristic, or most common meaning or interpretation associated with something else.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626ef711c8190a6bdbeda057af66a |
completed | May 2, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 10:52 a.m.