Triple
T28667119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miskatonic University |
E725611
|
entity |
| Predicate | hasMottoFandom |
P23882
|
FINISHED |
| Object | Ex Ignorantia Ad Sapientiam; Ex Luce Ad Tenebras |
—
|
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: Ex Ignorantia Ad Sapientiam; Ex Luce Ad Tenebras | Statement: [Miskatonic University, hasMottoFandom, Ex Ignorantia Ad Sapientiam; Ex Luce Ad Tenebras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoFandom Context triple: [Miskatonic University, hasMottoFandom, Ex Ignorantia Ad Sapientiam; Ex Luce Ad Tenebras]
-
A.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
B.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
C.
hasMottoInText
chosen
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
D.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
E.
hasMottoScript
Indicates that an entity’s motto is written or expressed in a particular writing system or script.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 28, 2026, 5:01 a.m.