Triple
T35691620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamestown Jammers |
E1031306
|
entity |
| Predicate | notableAffiliationPeriod |
—
|
GENERATED |
| Object | Pittsburgh Pirates 2013–2014 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAffiliationPeriod Context triple: [Jamestown Jammers, notableAffiliationPeriod, Pittsburgh Pirates 2013–2014]
-
A.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
B.
notableWorkPeriodStart
Indicates the point in time when an entity’s period of producing its notable work or works begins.
-
C.
notableOfficePeriod
Indicates that an entity held a particular office or position during a specified time period.
-
D.
notableEventPeriod
Indicates the time span during which a notable or significant event associated with an entity took place.
-
E.
notablePeriodOfInterest
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.