Triple
T11934914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lux et Veritas |
E284012
|
entity |
| Predicate | meaningOfComponentVeritas |
P60627
|
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: [Lux et Veritas, meaningOfComponentVeritas, truth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfComponentVeritas Context triple: [Lux et Veritas, meaningOfComponentVeritas, truth]
-
A.
veritasMeans
chosen
Indicates that one entity serves as the meaning, definition, or semantic content of another in the context of truth or correctness.
-
B.
LiberVeritatisFunction
Indicates a function or role associated with the "Liber Veritatis" that defines how it operates or is used in relation to other entities.
-
C.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
D.
definesVersionOf
Indicates that one entity specifies or establishes the version or variant identity of another entity.
-
E.
dataTypeVerified
Indicates that the data’s type has been checked and confirmed to match the expected or required type.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90306fcf48190a963d2d1932288d1 |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.