Triple
T25651770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decus et Veritas |
E643118
|
entity |
| Predicate | meaningContains |
P102770
|
FINISHED |
| Object | truth |
—
|
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: truth | Statement: [Decus et Veritas, meaningContains, truth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningContains Context triple: [Decus et Veritas, meaningContains, truth]
-
A.
meaningComponent
Indicates that one entity represents a semantic or conceptual component contributing to the overall meaning of another entity.
-
B.
meaningInContext
chosen
Indicates that one entity represents or conveys a particular meaning, interpretation, or sense within a specific context or situation.
-
C.
meaningViaRebecca
Indicates a relationship where something is understood, interpreted, or conveyed specifically through the mediation or perspective of Rebecca.
-
D.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
-
E.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa88aec819082bca8efba424a91 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 6:25 p.m.