Triple
T32350390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibson L-5 |
E826577
|
entity |
| Predicate | laterElectricVersions |
P12594
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Gibson L-5, laterElectricVersions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterElectricVersions Context triple: [Gibson L-5, laterElectricVersions, true]
-
A.
notableElectricVariant
chosen
Indicates that one entity is a notable or significant electric-powered version or variant of another entity.
-
B.
laterEquipment
Indicates that one piece of equipment occurs, is installed, or is used at a later time than another piece of equipment.
-
C.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
D.
laterEquipmentType
Indicates that one equipment type occurs or is used at a later time relative to another equipment type.
-
E.
laterPowerType
Indicates that one entity represents a power type that occurs or is defined at a later stage or level relative to another power type.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: May 1, 2026, 12:49 a.m.