Triple
T21872615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far East Family Band |
E540044
|
entity |
| Predicate | hasNotableGenreDescriptor |
P28041
|
FINISHED |
| Object | cosmic rock |
—
|
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: cosmic rock | Statement: [Far East Family Band, hasNotableGenreDescriptor, cosmic rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGenreDescriptor Context triple: [Far East Family Band, hasNotableGenreDescriptor, cosmic rock]
-
A.
hasNotableGenre
chosen
Indicates that an entity is significantly associated with a particular genre, such that the genre is especially characteristic or noteworthy for that entity.
-
B.
hasNotableGenreContext
Indicates that an entity’s genre is significant or noteworthy in understanding its context, interpretation, or impact.
-
C.
hasNotableSubgenre
Indicates that one genre is recognized as a particularly significant or prominent subgenre of another genre.
-
D.
hasGenreFeature
Indicates that something possesses a characteristic, element, or trait associated with a particular genre.
-
E.
hasMainGenre
Indicates that an entity’s primary or most characteristic genre is the specified genre.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f337ab5c8190937a457d348c732b |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7 p.m.