Triple
T18791119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merge sort |
E459515
|
entity |
| Predicate | worksWellFor |
P133020
|
FINISHED |
| Object | linked lists |
—
|
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: linked lists | Statement: [Merge sort, worksWellFor, linked lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksWellFor Context triple: [Merge sort, worksWellFor, linked lists]
-
A.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
B.
worksAs
Indicates that an entity performs the role, job, or occupation specified by another entity.
-
C.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
D.
worksThrough
Indicates that one entity performs an action, causes an effect, or achieves a result by using, employing, or acting via another entity as an intermediary or means.
-
E.
worksAgainst
Indicates that one entity actively opposes, counteracts, or undermines the goals, effects, or interests of another entity.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978665388190aaefed0ec30a1ff3 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.