Triple
T9218008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortius |
E221288
|
entity |
| Predicate | positiveForm |
P31278
|
FINISHED |
| Object | fortis |
—
|
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: fortis | Statement: [Fortius, positiveForm, fortis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positiveForm Context triple: [Fortius, positiveForm, fortis]
-
A.
hasPositiveForm
chosen
Indicates that one form, variant, or expression is the positive (non-comparative, non-superlative, or affirmative) version of another.
-
B.
negativeFormulation
Indicates that the associated statement, condition, or requirement is expressed in a negated or prohibitive form rather than an affirmative one.
-
C.
neutralized
Indicates that one entity has rendered another entity ineffective, harmless, or no longer able to exert its intended effect.
-
D.
negativeType
Indicates that one entity is classified as a negative, undesirable, or disfavored type in relation to another or within a given context.
-
E.
negativePhaseAssociatedWith
Indicates an association between something and a negative or unfavorable phase, state, or stage in a process or condition.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda0ae3d081908ff3f5dab52df5ae |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.