Triple
T26255156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stern–Brocot tree |
E656695
|
entity |
| Predicate | algorithmicUse |
P160166
|
FINISHED |
| Object | implementing binary search on rationals |
—
|
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: implementing binary search on rationals | Statement: [Stern–Brocot tree, algorithmicUse, implementing binary search on rationals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: algorithmicUse Context triple: [Stern–Brocot tree, algorithmicUse, implementing binary search on rationals]
-
A.
algorithmicUse
chosen
Indicates the use or application of an algorithmic process by one entity in relation to another entity or resource.
-
B.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
C.
algorithmicProperty
Indicates that a subject possesses a specific characteristic, behavior, or quality defined in terms of an algorithm or computational procedure.
-
D.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
-
E.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcd2e688190b54e36b0ff0d9187 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:08 p.m.