Triple
T20511798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LL8 |
E503582
|
entity |
| Predicate | redlineApprox |
P4460
|
FINISHED |
| Object | 6300 rpm |
—
|
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: 6300 rpm | Statement: [LL8, redlineApprox, 6300 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redlineApprox Context triple: [LL8, redlineApprox, 6300 rpm]
-
A.
redline
Indicates the act of refusing to offer services, opportunities, or fair treatment to certain people or areas based on discriminatory criteria such as race or neighborhood.
-
B.
referenceLineFor
Indicates a relationship where one entity serves as the baseline or standard line used as a point of reference for another entity.
-
C.
approximates
chosen
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
D.
yardLine
Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
-
E.
approximationRegion
Indicates a region or range within which a value, object, or condition is considered an acceptable approximation of a reference or target.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dcb8f5c8190b0d4c09f3669a8ec |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.