Triple
T18642720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fed |
E455728
|
entity |
| Predicate | bearerTurnedPro |
P9282
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Fed, bearerTurnedPro, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerTurnedPro Context triple: [Fed, bearerTurnedPro, 1998]
-
A.
turnedPro
chosen
Indicates that an individual transitioned from amateur status to professional status in a particular field or activity.
-
B.
premiumTierBackedBy
Indicates that a premium tier is supported, guaranteed, or underwritten by a specified backing entity or resource.
-
C.
isPremium
Indicates that an entity has premium status, typically granting enhanced or paid-tier features or privileges compared to a standard version.
-
D.
bearerFounded
Indicates that the bearer (such as a person or organization) is the one who established or created the associated entity (such as a company, institution, or project).
-
E.
couldBePromotedTo
Indicates a potential or eligibility for one entity to be advanced or elevated to a higher role, status, or position relative to another.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fcd6da081908030b052727f2c2f |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.