Triple
T30863872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tina Brooks |
E786137
|
entity |
| Predicate | notableRecordingPeriod |
P100607
|
FINISHED |
| Object | late 1950s |
—
|
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: late 1950s | Statement: [Tina Brooks, notableRecordingPeriod, late 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRecordingPeriod Context triple: [Tina Brooks, notableRecordingPeriod, late 1950s]
-
A.
hasNotableRecordingPeriod
chosen
Indicates that an entity is associated with a specific time span during which notable recording activity took place.
-
B.
notableEventPeriod
Indicates the time span during which a notable or significant event associated with an entity took place.
-
C.
notablePeriodOfInterest
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
-
D.
notablePopularityPeriod
Indicates the time span during which something was especially popular or widely recognized.
-
E.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:47 p.m.