Triple
T32759464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | @candiceswanepoel |
E837714
|
entity |
| Predicate | hasHighlights |
P197489
|
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, hasHighlights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighlights Context triple: [@candiceswanepoel, hasHighlights, yes]
-
A.
hasHighlightsFrom
Indicates that one entity contains or presents notable excerpts, key moments, or summarized points derived from another entity.
-
B.
hasHighlightGoal
Indicates that an entity has a primary or emphasized goal that is singled out as especially important or noteworthy.
-
C.
highlightsType
Indicates that one entity serves as a representative example or instance of the type or category defined by another entity.
-
D.
isConsideredHighlightOf
Indicates that something is regarded as the most notable, important, or outstanding part of another thing or event.
-
E.
highlightsSign
Indicates that one entity visually emphasizes or draws special attention to a sign.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
| PDg | Predicate description generation | batch_69fe96c0b760819093737292d33df165 |
completed | May 9, 2026, 2:06 a.m. |
Created at: May 1, 2026, 1:13 a.m.