Triple
T27935490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The 070 Project: Chapter 1 |
E708095
|
entity |
| Predicate | notableMemberFeatured |
P131218
|
FINISHED |
| Object | 070 Shake |
—
|
NE NERFINISHED |
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: 070 Shake | Statement: [The 070 Project: Chapter 1, notableMemberFeatured, 070 Shake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMemberFeatured Context triple: [The 070 Project: Chapter 1, notableMemberFeatured, 070 Shake]
-
A.
notableFigureFeatured
chosen
Indicates that a notable or prominent individual is highlighted, showcased, or given special attention in the associated context or medium.
-
B.
notableMemberVariant
Indicates that an entity is a specific variant or version of a notable member within a group, class, or category.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
-
E.
notableAppearanceFeature
Indicates that an entity is characterized by a distinctive or noteworthy physical appearance trait.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a0059f4ffe481908dc500cee9051148 |
completed | May 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a00593a3c1881909b2ff1a29eb474b3 |
completed | May 10, 2026, 10:08 a.m. |
Created at: April 27, 2026, 7:05 p.m.