Triple
T8163061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TokuDB |
E190622
|
entity |
| Predicate | usesIndexingTechnique |
P3047
|
FINISHED |
| Object | Fractal Tree indexing |
—
|
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: Fractal Tree indexing | Statement: [TokuDB, usesIndexingTechnique, Fractal Tree indexing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIndexingTechnique Context triple: [TokuDB, usesIndexingTechnique, Fractal Tree indexing]
-
A.
hasIndexing
Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
-
B.
usesSearchTechnologyFrom
Indicates that one entity employs or relies on the search technology developed or provided by another entity.
-
C.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
D.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
E.
indexingService
Indicates a service that organizes, catalogs, and maintains an index of items or data so they can be efficiently searched and retrieved.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4557ebc88190b4e2cab258374d23 |
completed | March 31, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.