Triple
T7727084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibson F-5 style mandolin |
E175156
|
entity |
| Predicate | hasIntroductionPeriod |
P60853
|
FINISHED |
| Object | early 1920s |
—
|
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: early 1920s | Statement: [Gibson F-5 style mandolin, hasIntroductionPeriod, early 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntroductionPeriod Context triple: [Gibson F-5 style mandolin, hasIntroductionPeriod, early 1920s]
-
A.
approximateIntroductionPeriod
chosen
Indicates the approximate time period during which an entity was first introduced or came into use.
-
B.
hasDiscoveryPeriod
Indicates the time span during which a particular discovery was made or recognized.
-
C.
hasFormulationPeriod
Indicates the time span during which something is planned, designed, or developed before it is finalized or implemented.
-
D.
hasRevelationPeriod
Indicates the time span or phase during which a revelation, disclosure, or unveiling of something occurs or is valid.
-
E.
hasIntroduction
Indicates that one entity includes or provides an introductory section, part, or presentation for another entity.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:06 p.m.