Triple
T32759463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | @candiceswanepoel |
E837714
|
entity |
| Predicate | hasStories |
P11859
|
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, hasStories, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStories Context triple: [@candiceswanepoel, hasStories, yes]
-
A.
hasBackupStories
Indicates that an entity maintains additional, alternative stories or narratives that can be used if the primary ones fail or are unavailable.
-
B.
hasNarrative
chosen
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
C.
hasVariantStoriesIn
Indicates that an entity has alternative or differing narrative versions that occur or are found within a specified context or source.
-
D.
hasInfluentialStory
Indicates that one entity possesses or is associated with a story that significantly shapes, impacts, or guides the beliefs, actions, or development of another entity.
-
E.
hasPrimaryStory
Indicates that one entity is designated as the main or most important story associated with 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_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 1, 2026, 1:13 a.m.