Triple
T32350346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES-175 |
E826576
|
entity |
| Predicate | originalPickupType |
P203537
|
FINISHED |
| Object | P-90 single-coil |
—
|
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: P-90 single-coil | Statement: [ES-175, originalPickupType, P-90 single-coil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPickupType Context triple: [ES-175, originalPickupType, P-90 single-coil]
-
A.
originalPickupSelector
Indicates the entity that was initially chosen or designated as the pickup point before any subsequent changes or updates.
-
B.
typicalPickupType
Indicates the usual or standard method by which an item or order is collected or picked up.
-
C.
pickupType
Indicates the manner or method by which an item or person is collected or retrieved (e.g., in-store pickup, curbside, scheduled pickup).
-
D.
usesPickupType
Indicates that one entity employs or operates a specific type of pickup in performing its function or action.
-
E.
laterPickupType
Indicates that the associated pickup occurs at a later time or belongs to a category of pickups scheduled after an initial or standard pickup.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a019dfc69fc8190b0d80279a6216ba7 |
completed | May 11, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_6a019d54586c81908292d4880db9fad2 |
completed | May 11, 2026, 9:11 a.m. |
| PDg | Predicate description generation | batch_6a019dfba430819089f5609d89fbb7d9 |
completed | May 11, 2026, 9:14 a.m. |
Created at: May 1, 2026, 12:49 a.m.