Triple
T29636479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Water Transit |
E755727
|
entity |
| Predicate | hasApproximateProductionPeriod |
P23186
|
FINISHED |
| Object | mid-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: mid-2000s | Statement: [Black Water Transit, hasApproximateProductionPeriod, mid-2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateProductionPeriod Context triple: [Black Water Transit, hasApproximateProductionPeriod, mid-2000s]
-
A.
timePeriodOfProduction
chosen
Indicates the span of time during which something was produced or created.
-
B.
mainProductionPeriodStart
Indicates the point in time when the primary or main phase of production for something begins.
-
C.
approximateProductionNumber
Indicates that one entity specifies an estimated or non-exact quantity associated with the production output of another entity.
-
D.
modelProduced
Indicates that a particular model has generated or produced a specified output, result, or artifact.
-
E.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 6:44 p.m.