Triple
T21494159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermat primality test |
E530310
|
entity |
| Predicate | hasErrorType |
P144597
|
FINISHED |
| Object | false 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: false positive | Statement: [Fermat primality test, hasErrorType, false positive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasErrorType Context triple: [Fermat primality test, hasErrorType, false positive]
-
A.
hasGoodType
Indicates that an entity possesses a type or classification considered appropriate, valid, or of high quality according to some defined criteria.
-
B.
hasExceptionFor
Indicates that a general rule, condition, or behavior does not apply in a particular case or under specific circumstances.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasStandardType
Indicates that something conforms to or is categorized under a defined standard classification or type.
-
E.
hasCurrentType
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
- F. None of above. chosen
Provenance (4 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea567244819091863350fedae3ae |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:23 p.m.