Triple
T1682753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IGTV |
E36372
|
entity |
| Predicate | contentDiscovery |
P19729
|
FINISHED |
| Object | algorithmic recommendations |
—
|
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: algorithmic recommendations | Statement: [IGTV, contentDiscovery, algorithmic recommendations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentDiscovery Context triple: [IGTV, contentDiscovery, algorithmic recommendations]
-
A.
discovery
chosen
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
B.
primaryContent
Indicates that one entity serves as the main or most important content associated with another entity.
-
C.
featuresTopic
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
-
D.
contentProvider
Indicates that one entity serves as the source or supplier of content (such as media, information, or data) for another entity.
-
E.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.