Triple
T27590988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elasticsearch |
E699787
|
entity |
| Predicate | supportsClusterRole |
P10797
|
FINISHED |
| Object | master-eligible node |
—
|
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: master-eligible node | Statement: [Elasticsearch, supportsClusterRole, master-eligible node]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsClusterRole Context triple: [Elasticsearch, supportsClusterRole, master-eligible node]
-
A.
supportsClusterManagement
Indicates that one entity provides functionality or resources that enable the management and coordination of a cluster of related entities.
-
B.
supportsRole
chosen
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
C.
roleInCluster
Indicates the specific function or position an entity holds within a defined group or cluster of related entities.
-
D.
supportsMultiplePowerRoles
Indicates that an entity can simultaneously handle or be assigned more than one distinct power-related role.
-
E.
appliesToAdministrativeRole
Indicates that something is relevant or applicable specifically to an administrative role or position.
- 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_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:05 p.m.