Triple
T32670026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fides quaerens intellectum |
E835266
|
entity |
| Predicate | notablyExpressedIn |
P205133
|
FINISHED |
| Object | Proslogion |
E200679
|
NE 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: Proslogion | Statement: [Fides quaerens intellectum, notablyExpressedIn, Proslogion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablyExpressedIn Context triple: [Fides quaerens intellectum, notablyExpressedIn, Proslogion]
-
A.
tissueExpression
Indicates the association between a biological entity (such as a gene or protein) and the specific tissue(s) in which it is expressed.
-
B.
expressedInCellType
Indicates that something (such as a gene, protein, or molecule) is expressed or present in a specified cell type.
-
C.
expressedInSpecies
Indicates that something (such as a gene, protein, or trait) is observed or manifested in a particular species.
-
D.
alsoExpressedIn
Indicates that something which is expressed in one context, medium, or entity is likewise expressed in another.
-
E.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
- F. None of above. chosen
Provenance (5 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a349eb4ab288190bd21b3bc8275b4c0 |
completed | June 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:09 a.m.