Triple
T4619989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linsanity |
E100952
|
entity |
| Predicate | endedOrDeclinedAfter |
P57040
|
FINISHED |
| Object | Jeremy Lin’s knee injury in 2012 |
—
|
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: Jeremy Lin’s knee injury in 2012 | Statement: [Linsanity, endedOrDeclinedAfter, Jeremy Lin’s knee injury in 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedOrDeclinedAfter Context triple: [Linsanity, endedOrDeclinedAfter, Jeremy Lin’s knee injury in 2012]
-
A.
declinedDuring
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
B.
declinedAround
Indicates that something decreased in value, intensity, or quantity in the time period surrounding a specified point or event.
-
C.
declineAfter
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
D.
declineBeganInPeriod
Indicates that the onset of a decline in the subject occurred during the specified time period.
-
E.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e3e6948190925e2cfad20dcc8c |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:12 p.m.