Triple
T31077845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vicus Portae Quirinalis |
E792016
|
entity |
| Predicate | certaintyOfCourse |
P148087
|
FINISHED |
| Object | uncertain |
—
|
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: uncertain | Statement: [vicus Portae Quirinalis, certaintyOfCourse, uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: certaintyOfCourse Context triple: [vicus Portae Quirinalis, certaintyOfCourse, uncertain]
-
A.
hasCertainty
Indicates that a statement, belief, or relationship is associated with a specific level or degree of confidence or surety.
-
B.
narrativeCertainty
Indicates the degree of confidence or definitiveness with which a narrative, statement, or account is presented as true or reliable.
-
C.
maintainsBeliefDespite
Indicates that an entity continues to hold a particular belief even in the face of opposing evidence, pressure, or changing circumstances.
-
D.
confidenceLevel
chosen
Indicates the degree of certainty or assurance associated with a particular claim, decision, or outcome.
-
E.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695bbbaa081909fb1aa003e864c08 |
completed | May 3, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.