Triple
T35691620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamestown Jammers |
E1031306
|
entity |
| Predicate | notableAffiliationPeriod |
P207098
|
FINISHED |
| Object | Pittsburgh Pirates 2013–2014 |
—
|
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: Pittsburgh Pirates 2013–2014 | Statement: [Jamestown Jammers, notableAffiliationPeriod, Pittsburgh Pirates 2013–2014]
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 (4 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:05 p.m.