Triple
T759466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Pirates |
E16032
|
entity |
| Predicate | homeOpeningSeason |
P16999
|
FINISHED |
| Object | 1993–94 |
—
|
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: 1993–94 | Statement: [Portland Pirates, homeOpeningSeason, 1993–94]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeOpeningSeason Context triple: [Portland Pirates, homeOpeningSeason, 1993–94]
-
A.
openSeason
Indicates that a period has begun during which a particular activity (such as hunting, fishing, or competition) is officially allowed or actively underway.
-
B.
homeFieldOpened
Indicates that a team's designated home field has officially begun operation or been opened for use.
-
C.
startSeason
chosen
Indicates the point in time or event at which a particular season begins.
-
D.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
E.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a67f9778819098d3c144dd26b976 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.