Triple
T27888485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NodeManager |
E705289
|
entity |
| Predicate | hasConfigurationProperty |
P23698
|
FINISHED |
| Object | yarn.nodemanager.resource.memory-mb |
—
|
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: yarn.nodemanager.resource.memory-mb | Statement: [NodeManager, hasConfigurationProperty, yarn.nodemanager.resource.memory-mb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConfigurationProperty Context triple: [NodeManager, hasConfigurationProperty, yarn.nodemanager.resource.memory-mb]
-
A.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
hasConfigurationName
Indicates that an entity is associated with or identified by a specific configuration name.
-
C.
hasConfigurationFile
Indicates that an entity is associated with or defined by a specific configuration file.
-
D.
hasSubconfiguration
Indicates that an entity includes another entity as a subordinate or component configuration within its overall structure.
-
E.
haveProperty
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: April 27, 2026, 6:34 p.m.