Triple
T18896748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoare partition scheme |
E462227
|
entity |
| Predicate | partitionStrategy |
P58206
|
FINISHED |
| Object | two indices moving toward each other |
—
|
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: two indices moving toward each other | Statement: [Hoare partition scheme, partitionStrategy, two indices moving toward each other]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partitionStrategy Context triple: [Hoare partition scheme, partitionStrategy, two indices moving toward each other]
-
A.
partitionProperty
Indicates that a specified property defines how a set or resource is divided into distinct partitions or segments.
-
B.
partitionScheme
chosen
Indicates how a whole is divided into distinct parts or segments according to a specific organizing scheme.
-
C.
transitionStrategy
Indicates the method or plan used to move from one state, phase, or condition to another.
-
D.
schedulingStrategy
Indicates how tasks, events, or operations are ordered and allocated over time or resources relative to one another.
-
E.
postPartitionUse
Indicates that something is used or occurs after a partition, division, or separation has taken place.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47f6c948190918ade08bb88f1fd |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.