Triple
T35741205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMT510 |
E1033037
|
entity |
| Predicate | productionPeriodApproximate |
P23186
|
FINISHED |
| Object | early 2000s |
—
|
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 2000s | Statement: [GMT510, productionPeriodApproximate, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionPeriodApproximate Context triple: [GMT510, productionPeriodApproximate, early 2000s]
-
A.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
B.
periodOfRelease
Indicates the time span or date range during which something (such as a work, product, or version) is officially released or made available.
-
C.
approximatePremiereYear
Indicates the estimated calendar year in which something, typically a work or event, first premiered.
-
D.
timePeriodOfProduction
chosen
Indicates the span of time during which something was produced or created.
-
E.
endYearApprox
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 3, 2026, 4:06 p.m.