Triple
T5752397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | r/pics |
E126882
|
entity |
| Predicate | supportsSortingBy |
P28010
|
FINISHED |
| Object | hot |
—
|
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: hot | Statement: [r/pics, supportsSortingBy, hot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSortingBy Context triple: [r/pics, supportsSortingBy, hot]
-
A.
hasSort
chosen
Indicates that one entity is associated with, or classified by, a particular sort, type, or category.
-
B.
supportsColumnSelectionBy
Indicates that one entity enables or provides functionality for another entity to select specific columns.
-
C.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
D.
endsBy
Indicates that one event, process, or state concludes precisely at the same time another specified event, process, or state ends.
-
E.
featuresOrder
Indicates that one entity specifies or determines the sequence or arrangement in which another entity’s features appear or are organized.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.