Triple
T14956546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flint Tropics |
E372943
|
entity |
| Predicate | hasSloganDepicted |
P89151
|
FINISHED |
| Object | Everybody love everybody |
—
|
LITERAL 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: Everybody love everybody | Statement: [Flint Tropics, hasSloganDepicted, Everybody love everybody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSloganDepicted Context triple: [Flint Tropics, hasSloganDepicted, Everybody love everybody]
-
A.
hasSloganType
Indicates the specific category or type of slogan associated with an entity.
-
B.
hasAdvertisingSlogan
chosen
Indicates that an entity uses or is associated with a particular advertising slogan as part of its promotional or branding activities.
-
C.
sloganGivenBy
Indicates that a particular slogan is provided, coined, or assigned by a specific entity.
-
D.
sloganUsedBy
Indicates that a particular slogan is employed or adopted by a specific entity (such as a person, organization, or brand) in its communication or branding.
-
E.
sloganUsedIn
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cc73848190ac181782b20dc838 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.