Triple
T32350347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES-175 |
E826576
|
entity |
| Predicate | laterPickupType |
P200473
|
FINISHED |
| Object | PAF humbucker |
—
|
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: PAF humbucker | Statement: [ES-175, laterPickupType, PAF humbucker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPickupType Context triple: [ES-175, laterPickupType, PAF humbucker]
-
A.
laterPickupSelector
Indicates a choice or mechanism for selecting a pickup time that occurs later than an initial or default option.
-
B.
pickupOption
Indicates that one entity offers or selects a method or arrangement for collecting or retrieving another entity (such as goods, items, or services).
-
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.
hasPickup
Indicates that one entity is assigned or associated with a specific pickup location, time, or arrangement for collection.
-
E.
typicalPickupType
Indicates the usual or standard method by which an item or order is collected or picked up.
- 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_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69ff8cec1e4c8190b2d66b3e0f913bfd |
completed | May 9, 2026, 7:37 p.m. |
Created at: May 1, 2026, 12:49 a.m.