Triple
T36151588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVL tree |
E1045598
|
entity |
| Predicate | heightUpperBound |
P184762
|
FINISHED |
| Object | 1.44 log2(n+2) - 0.328 |
—
|
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: 1.44 log2(n+2) - 0.328 | Statement: [AVL tree, heightUpperBound, 1.44 log2(n+2) - 0.328]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightUpperBound Context triple: [AVL tree, heightUpperBound, 1.44 log2(n+2) - 0.328]
-
A.
heightRestriction
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
B.
heightDescription
Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
-
C.
heightOptions
Indicates the available or specified height choices associated with an entity or configuration.
-
D.
heightRestrictionWithCompanion
Indicates that there is a height-based restriction which may be satisfied or modified when the person is accompanied by a qualifying companion.
-
E.
heightClass
Indicates the categorical height level or range to which an entity is assigned (e.g., short, medium, tall).
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b3e0f1c88190985feab6cee8b05e |
completed | May 3, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:08 p.m.