Triple
T31159563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Eraser live band |
E794301
|
entity |
| Predicate | laterKnownCollectivelyAs |
P144948
|
FINISHED |
| Object | Atoms for Peace |
—
|
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: Atoms for Peace | Statement: [The Eraser live band, laterKnownCollectivelyAs, Atoms for Peace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterKnownCollectivelyAs Context triple: [The Eraser live band, laterKnownCollectivelyAs, Atoms for Peace]
-
A.
laterBecameKnownAs
chosen
Indicates that an entity was previously known by one name or identity and, at a later time, came to be known by a different name or identity.
-
B.
collectivelyKnownAs
Indicates that multiple entities are referred to together under a single shared name or designation.
-
C.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
D.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
E.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: April 29, 2026, 9:07 p.m.