Triple
T34856889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baylee Marie Roethlisberger |
E1004749
|
entity |
| Predicate | parentPlayedFor |
P195285
|
FINISHED |
| Object | Pittsburgh Steelers |
—
|
NE NERFINISHED |
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 Steelers | Statement: [Baylee Marie Roethlisberger, parentPlayedFor, Pittsburgh Steelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentPlayedFor Context triple: [Baylee Marie Roethlisberger, parentPlayedFor, Pittsburgh Steelers]
-
A.
playedWhile
Indicates that one activity or event occurred concurrently with another, with the second serving as the temporal context during which the first was performed.
-
B.
playedAfter
Indicates that one event, performance, or action occurred later in time than another.
-
C.
playedFrom
Indicates that an action of playing (such as media playback or a performance) originated from a particular source or starting point.
-
D.
hasBeenPlayedAt
Indicates that an entity (such as a song, track, or media item) has been performed or broadcast at a particular time, place, or event.
-
E.
wasPlayed
Indicates that an entity (such as a game, song, or media item) was performed, executed, or used by someone or something.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
| PDg | Predicate description generation | batch_69fdb4544b548190b8971f8055d48caa |
completed | May 8, 2026, 10 a.m. |
Created at: May 3, 2026, 4 p.m.