Triple
T23950162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Bulls vs Detroit Pistons |
E603023
|
entity |
| Predicate | notablePeriodEnd |
P34836
|
FINISHED |
| Object | 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: early 1990s | Statement: [Chicago Bulls vs Detroit Pistons, notablePeriodEnd, early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePeriodEnd Context triple: [Chicago Bulls vs Detroit Pistons, notablePeriodEnd, early 1990s]
-
A.
documentedPeriodEnd
Indicates the point in time at which the documented period or interval associated with something comes to an end.
-
B.
narrativePeriodEnd
Indicates the point in time at which a described narrative, story, or event sequence comes to an end.
-
C.
associatedPeriodEnd
chosen
Indicates the ending point or final date of the time period with which something is associated.
-
D.
notablePeriodOfInterest
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
-
E.
notableEventPeriod
Indicates the time span during which a notable or significant event associated with an entity took place.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d03140f08190b4356626628ff56f |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:19 p.m.