Triple
T33346446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Street |
E853807
|
entity |
| Predicate | statusOnTeam |
P3500
|
FINISHED |
| Object | starting quarterback |
—
|
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: starting quarterback | Statement: [Jason Street, statusOnTeam, starting quarterback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOnTeam Context triple: [Jason Street, statusOnTeam, starting quarterback]
-
A.
teamState
Indicates the current status or condition of a team within a given context or process.
-
B.
officialStatusWithTeam
chosen
Indicates that an entity holds or has held an official role, position, or status in relation to a specific team.
-
C.
statusGroup
Indicates a classification relationship where an entity is assigned to or associated with a particular status category or group.
-
D.
clubStatus
Indicates the current standing or role an entity holds within a club, such as membership level, activity state, or official position.
-
E.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: May 1, 2026, 1:34 a.m.