Triple
T12514464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | uniq |
E299160
|
entity |
| Predicate | commonPipelineUse |
P4791
|
FINISHED |
| Object | often used in combination with sort |
—
|
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: often used in combination with sort | Statement: [uniq, commonPipelineUse, often used in combination with sort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonPipelineUse Context triple: [uniq, commonPipelineUse, often used in combination with sort]
-
A.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
-
B.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
C.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
D.
usedWith
chosen
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
E.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.