Triple
T27590985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elasticsearch |
E699787
|
entity |
| Predicate | supportsIndexingMode |
P99857
|
FINISHED |
| Object | bulk 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: bulk indexing | Statement: [Elasticsearch, supportsIndexingMode, bulk indexing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIndexingMode Context triple: [Elasticsearch, supportsIndexingMode, bulk indexing]
-
A.
hasIndexing
Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
-
B.
usesIndexation
Indicates that one entity applies or relies on an indexing scheme or index-based method provided by or associated with another entity.
-
C.
isIndexedFor
Indicates that something has been organized or recorded in an index so it can be efficiently located, searched, or retrieved.
-
D.
allowsIndexInclusion
Indicates that one entity permits another entity to be included or listed within an index or indexing system.
-
E.
supportedMode
chosen
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: April 27, 2026, 2:05 p.m.