Triple
T31822009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Lucky Beavers |
E812286
|
entity |
| Predicate | usedAsNameInEra |
P145623
|
FINISHED |
| Object | early years of Portland Beavers franchise |
—
|
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 years of Portland Beavers franchise | Statement: [Portland Lucky Beavers, usedAsNameInEra, early years of Portland Beavers franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsNameInEra Context triple: [Portland Lucky Beavers, usedAsNameInEra, early years of Portland Beavers franchise]
-
A.
usedEraName
Indicates that an entity employed or referenced a specific historical or calendrical era name in its dating or designation.
-
B.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
-
C.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
-
D.
historicalNameUsedIn
chosen
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
E.
precedesEraName
Indicates that one era occurs entirely before another era in chronological order.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 30, 2026, 11:46 p.m.