Triple
T5310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veritas |
E104
|
entity |
| Predicate | usedInContext |
P36
|
FINISHED |
| Object | academic motto |
—
|
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: academic motto | Statement: [Veritas, usedInContext, academic motto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInContext Context triple: [Veritas, usedInContext, academic motto]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
context
chosen
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
C.
influenced
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
-
D.
near
Indicates that one entity is located at a short distance from another entity in space or position.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23c24b3d08190a714126292fd5479 |
completed | Feb. 28, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69a23998af288190855f0456740cbd51 |
completed | Feb. 28, 2026, 12:40 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.