Triple
T17234174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instagram main feed |
E418317
|
entity |
| Predicate | sortingBasis |
P12242
|
FINISHED |
| Object | user engagement signals |
—
|
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: user engagement signals | Statement: [Instagram main feed, sortingBasis, user engagement signals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sortingBasis Context triple: [Instagram main feed, sortingBasis, user engagement signals]
-
A.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
B.
submissionSortingOptions
Indicates how submissions are ordered or prioritized according to specified sorting criteria.
-
C.
socialOrder
Indicates the hierarchical or structured arrangement of roles, statuses, and power relations that organize interactions within a society or group.
-
D.
endsBy
Indicates that one event, process, or state concludes precisely at the same time another specified event, process, or state ends.
-
E.
rankingType
chosen
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dfa0a408190880804d463305867 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.