Triple
T37054151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Like Digging? (as Kara's Flowers) |
E917128
|
entity |
| Predicate | hasMemberAtTimeOfRecording |
P22071
|
FINISHED |
| Object | Adam Levine |
—
|
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: Adam Levine | Statement: [We Like Digging? (as Kara's Flowers), hasMemberAtTimeOfRecording, Adam Levine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberAtTimeOfRecording Context triple: [We Like Digging? (as Kara's Flowers), hasMemberAtTimeOfRecording, Adam Levine]
-
A.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
B.
hasMemberWhoBecame
Indicates that a group or organization includes at least one member who later attained or transitioned into a specified role, status, or affiliation.
-
C.
bandMemberOnRecording
chosen
Indicates that a person is a member of a band who performed on a specific recording.
-
D.
hasMemberInvolvedIn
Indicates that a group or collective entity has at least one of its members participating in or engaged with a specified activity, event, or situation.
-
E.
hasMemberAlsoIn
Indicates that an entity has at least one member who also belongs to another specified group or collection.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 3, 2026, 4:14 p.m.