Triple
T3507276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AlexNet |
E74105
|
entity |
| Predicate | top5ErrorRate |
P48403
|
FINISHED |
| Object | 15.3% |
—
|
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: 15.3% | Statement: [AlexNet, top5ErrorRate, 15.3%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: top5ErrorRate Context triple: [AlexNet, top5ErrorRate, 15.3%]
-
A.
trackingErrorCharacteristic
Indicates the specific type or nature of the discrepancy between a tracked value and its reference or target over time.
-
B.
reachedCategory5On
Indicates that an entity attained Category 5 intensity or status on a specific date or at a specific time.
-
C.
successRate
Indicates the proportion or frequency with which attempts at a given action or process result in a successful outcome.
-
D.
topTierUntil
Indicates that an entity holds a top-tier or highest-status position only up to a specified point in time, after which this status no longer applies.
-
E.
errorType
Indicates the specific category or kind of error associated with an event, action, or entity.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc0b635c81909bc95ba2562d8f94 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:18 p.m.