Triple
T112012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Per Ardua ad Astra |
E2267
|
entity |
| Predicate | componentMeaning |
P3918
|
FINISHED |
| Object | Per Ardua means "through adversity" |
—
|
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: Per Ardua means "through adversity" | Statement: [Per Ardua ad Astra, componentMeaning, Per Ardua means "through adversity"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentMeaning Context triple: [Per Ardua ad Astra, componentMeaning, Per Ardua means "through adversity"]
-
A.
titleMeaning
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
B.
hasMean
Indicates that one entity possesses, exhibits, or is characterized by a particular mean value or average.
-
C.
hasLiteralMeaning
chosen
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
-
D.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
Article5Meaning
Indicates that a legal or policy document specifies the meaning, scope, or implications of its Article 5 provision.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.