Triple
T14169101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Non Incautus Futuri |
E351156
|
entity |
| Predicate | semanticPolarity |
P26308
|
FINISHED |
| Object | positive |
—
|
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: positive | Statement: [Non Incautus Futuri, semanticPolarity, positive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticPolarity Context triple: [Non Incautus Futuri, semanticPolarity, positive]
-
A.
polarity
chosen
Indicates whether the relationship or statement is affirmed (positive) or denied/opposed (negative).
-
B.
timePolarity
Indicates the temporal orientation of an event or state, such as whether it occurs in the past, present, or future relative to a reference time.
-
C.
logicalPolarity
Indicates that the truth value of a statement is affirmed (positive) or denied (negative) relative to some logical context.
-
D.
weightPolarity
Indicates how the direction or sign (positive or negative) of a weight or weighting factor affects the relationship or influence between entities.
-
E.
sentience
Indicates that an entity possesses the capacity for subjective experience, awareness, or feeling.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b472288190b4a271daa54aa6cd |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1 a.m.