Triple
T23937076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remember Love |
E602667
|
entity |
| Predicate | hasCompanionRoleTo |
P154426
|
FINISHED |
| Object | Give Peace a Chance |
—
|
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: Give Peace a Chance | Statement: [Remember Love, hasCompanionRoleTo, Give Peace a Chance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionRoleTo Context triple: [Remember Love, hasCompanionRoleTo, Give Peace a Chance]
-
A.
hasCompanionRoleIn
Indicates that an entity serves in a companion or supporting role within a specified context, activity, or relationship.
-
B.
hasCompanionActor
Indicates that one actor is accompanied or associated by another actor as a companion in a given context or activity.
-
C.
hasCompanionCandidate
Indicates that an entity is associated with another entity that is being considered or proposed as a potential companion.
-
D.
hasCompanionCharacterProfession
Indicates that a companion character is associated with or practices a particular profession.
-
E.
hasCompanionColleague
Indicates that one entity has another entity as a colleague who also serves as a companion or close associate.
- F. None of above. chosen
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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cfa1336c8190ac307a1b9497ba0b |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:05 p.m.