Triple
T1553297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veritas vos liberabit |
E33141
|
entity |
| Predicate | literalObject |
P3918
|
FINISHED |
| Object | you (plural) |
—
|
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: you (plural) | Statement: [Veritas vos liberabit, literalObject, you (plural)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literalObject Context triple: [Veritas vos liberabit, literalObject, you (plural)]
-
A.
hasLiteralMeaning
chosen
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
-
B.
lexicalItem
Indicates that one entity is a word or vocabulary unit associated with, or used to express, another entity (such as a concept, meaning, or linguistic entry).
-
C.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
-
D.
logicalTrait
Indicates that an entity possesses a characteristic, behavior, or quality related to logical reasoning or structured thinking.
-
E.
linguisticType
Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.