Triple
T15958139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stars Fell on Alabama |
E386987
|
entity |
| Predicate | hasStandardStatusBy |
P15010
|
FINISHED |
| Object | mid-20th century jazz musicians |
—
|
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: mid-20th century jazz musicians | Statement: [Stars Fell on Alabama, hasStandardStatusBy, mid-20th century jazz musicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardStatusBy Context triple: [Stars Fell on Alabama, hasStandardStatusBy, mid-20th century jazz musicians]
-
A.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
B.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
C.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
D.
hasStatusIn
chosen
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.