Triple
T4508605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Red Line |
E101993
|
entity |
| Predicate | differential |
P57076
|
FINISHED |
| Object | limited-slip differential (available) |
—
|
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: limited-slip differential (available) | Statement: [Sky Red Line, differential, limited-slip differential (available)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differential Context triple: [Sky Red Line, differential, limited-slip differential (available)]
-
A.
isDifferential
Indicates that one quantity represents the infinitesimal change or derivative of another with respect to a given variable.
-
B.
delta
Indicates a change, difference, or variation between two related quantities, states, or conditions.
-
C.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
D.
differentiatedFrom
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
-
E.
derivativeDesignation
Indicates that one entity is formally identified as a derivative or adapted version of another 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd570f9b1c8190b52ace855dbf6641 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:01 p.m.