Triple
T37053592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JJAMZ |
E917112
|
entity |
| Predicate | formedFromBand |
P25537
|
FINISHED |
| Object | Maroon 5 |
E53774
|
NE 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: Maroon 5 | Statement: [JJAMZ, formedFromBand, Maroon 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedFromBand Context triple: [JJAMZ, formedFromBand, Maroon 5]
-
A.
formedBandIn
Indicates the place or context in which a musical band was originally created or came together.
-
B.
originatedFromBand
chosen
Indicates that an entity (such as a musician or group) originally came from or was formed as part of a particular band.
-
C.
bandFormedWith
Indicates that two or more entities came together to create or establish a musical band as members or co-founders.
-
D.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
E.
associatedBandOrigin
Indicates that there is a relationship between a musical band and the geographic place from which that band originates or is closely associated.
- F. None of above.
Provenance (4 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00be8ee4bc8190b795d9606f0e490c |
completed | May 10, 2026, 5:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e8c4d51a08190ad308c80bffd8f71 |
completed | June 26, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a00bde163c88190867104bd08cac2ee |
completed | May 10, 2026, 5:18 p.m. |
Created at: May 3, 2026, 4:14 p.m.