Triple
T32759460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | @candiceswanepoel |
E837714
|
entity |
| Predicate | hasProfilePicture |
P170905
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [@candiceswanepoel, hasProfilePicture, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProfilePicture Context triple: [@candiceswanepoel, hasProfilePicture, yes]
-
A.
hasPhotoOn
Indicates that one entity has an associated photograph stored, displayed, or linked on another entity (such as a platform, page, or medium).
-
B.
hasPhotogenicProfileFrom
Indicates that an entity has a visually appealing or photogenic profile as captured or derived from a specified source or viewpoint.
-
C.
pictureProfile
chosen
Indicates that one entity serves as the profile picture or primary display image associated with another entity.
-
D.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
E.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: May 1, 2026, 1:13 a.m.