Triple
T5348092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black, Brown and Beige |
E124104
|
entity |
| Predicate | laterCriticalStatus |
P8082
|
FINISHED |
| Object | landmark in jazz composition |
—
|
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: landmark in jazz composition | Statement: [Black, Brown and Beige, laterCriticalStatus, landmark in jazz composition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCriticalStatus Context triple: [Black, Brown and Beige, laterCriticalStatus, landmark in jazz composition]
-
A.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
B.
majorStatus
Indicates that an entity holds primary or most significant status relative to others in a given context.
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
laterOperationalIssue
Indicates that an operational issue occurred at some point after a referenced time, event, or condition.
-
E.
criticalReputation
chosen
Indicates that an entity is regarded by critics with a particular level or type of esteem, evaluation, or standing based on critical assessments.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ef75148190815461c2a49302e9 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.