Triple
T7342325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Norwood |
E169283
|
entity |
| Predicate | playedForDuration |
P22584
|
FINISHED |
| Object | Buffalo Bills in the late 1980s and early 1990s |
—
|
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: Buffalo Bills in the late 1980s and early 1990s | Statement: [Scott Norwood, playedForDuration, Buffalo Bills in the late 1980s and early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedForDuration Context triple: [Scott Norwood, playedForDuration, Buffalo Bills in the late 1980s and early 1990s]
-
A.
playedUntil
Indicates that an action or event involving playing continued up to a specific time, point, or condition.
-
B.
playedAfter
Indicates that one event, performance, or action occurred later in time than another.
-
C.
playedInPeriod
chosen
Indicates that an entity participated or was active during a specified time period.
-
D.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
E.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.