Triple
T27734064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hashtable |
E697490
|
entity |
| Predicate | resizingBehavior |
P58733
|
FINISHED |
| Object | grows as needed when load factor is exceeded |
—
|
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: grows as needed when load factor is exceeded | Statement: [Hashtable, resizingBehavior, grows as needed when load factor is exceeded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resizingBehavior Context triple: [Hashtable, resizingBehavior, grows as needed when load factor is exceeded]
-
A.
rangeBehavior
Indicates how an entity behaves or operates when interacting with or within a specified range or distance.
-
B.
limitBehavior
Indicates how an entity behaves or changes as it approaches a specified limit or boundary condition.
-
C.
raidSizeMode
Indicates how the size or scale of a raid is determined or configured (e.g., fixed, flexible, or dynamically adjusted).
-
D.
scalingProperty
chosen
Indicates how a quantity or behavior changes in proportion to changes in another variable, typically under resizing or rescaling conditions.
-
E.
widthDependsOn
Indicates that the width of one entity is determined or constrained by the width or properties of another entity.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369fa1d88190ac40370ec4fa185e |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:12 p.m.